From kfm-devel Fri Dec 23 04:38:19 2005 From: Dawit Alemayehu Date: Fri, 23 Dec 2005 04:38:19 +0000 To: kfm-devel Subject: Content-Location non-bug/bug dilemma Message-Id: <200512222338.19523.adwa () cox ! net> X-MARC-Message: https://marc.info/?l=kfm-devel&m=113532352401785 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--Boundary-00=_783qDzxGHCEOj8W" --Boundary-00=_783qDzxGHCEOj8W Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, The following patch is meant to address BR# 82747: http://bugs.kde.org/show_bug.cgi?id=82747 It reverts a patch that fixed BR# 51185: http://bugs.kde.org/show_bug.cgi?id=51185 Following a standard is worthless if we are the only ones that do it. Every other major browser seems to break this. At least Mozilla/Firefox does. Anyways, I want to bring this up for discussion here because this breaks starndard compliant behavior. -- Regards, Dawit A. --Boundary-00=_783qDzxGHCEOj8W Content-Type: text/x-diff; charset="iso-8859-1"; name="khtml_20051222.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="khtml_20051222.diff" Index: khtml_part.cpp =================================================================== --- khtml_part.cpp (revision 490608) +++ khtml_part.cpp (working copy) @@ -1643,10 +1643,14 @@ if( !qData.isEmpty()) d->m_doc->processHttpEquiv("refresh", qData); - // Support Content-Location per section 14.14 of RFC 2616. + // DISABLED: Support Content-Location per section 14.14 of RFC 2616. See BR# 51185 + // NOTE: This has been disabled because none of the other major browsers follow it! + // Following standards is useless if we are the only ones that does it. See BR# 82747 + /* QString baseURL = d->m_job->queryMetaData ("content-location"); if (!baseURL.isEmpty()) d->m_doc->setBaseURL(KURL( d->m_doc->completeURL(baseURL) )); + */ if ( !m_url.isLocalFile() ) { // Support for http last-modified --Boundary-00=_783qDzxGHCEOj8W--