Bug 117448 - some types of redirects are failing
Summary: some types of redirects are failing
Status: RESOLVED DUPLICATE of bug 82747
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-01 18:42 UTC by Pedro de Oliveira
Modified: 2005-12-01 19:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro de Oliveira 2005-12-01 18:42:14 UTC
Version:           3.5 (using KDE 3.5.0, Gentoo)
Compiler:          gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)
OS:                Linux (i686) release 2.6.14-gentoo

Konqueror is failing on two MAJOR portuguese online shops. I think they use some kind of weird redirection that konqueror doesnt support.

The two sites are: www.worten.pt and www.vobis.pt

when you open the sites on konqueror the url is changed to:
http://www.worten.pt:8889/home.html
http://www.vobis.pt:8890/vobis/main/home.jsp

and they dont work that way, this bug existed in 3.4 too, i didnt reported it earlier because i tought it would be fixed in 3.5

Btw, i've read the other bug reports and i didnt found out any one like this , thats why i reported.

Regards, if you need any adittional info, please ask!
Comment 1 Thiago Macieira 2005-12-01 18:52:20 UTC
Not a KDE bug. The bug is on the website itself. Note the Content-Location header in the reply:

kio_http: (14904) ============ Received Response:
kio_http: (14904) "HTTP/1.1 200 OK"
kio_http: (14904) "Date: Thu, 01 Dec 2005 17:50:33 GMT"
kio_http: (14904) "Server: Microsoft-IIS/4.0"
kio_http: (14904) "Content-Location: http://www.worten.pt:8889/default.htm"
kio_http: (14904) "Content-Type: text/html; charset=ISO-8859-1"
kio_http: (14904) "Accept-Ranges: bytes"
kio_http: (14904) "Last-Modified: Tue, 30 Apr 2002 10:36:11 GMT"
kio_http: (14904) "ETag: "4aba78d832f0c11:b600""
kio_http: (14904) "Content-Length: 179"


*** This bug has been marked as a duplicate of 82747 ***
Comment 2 Pedro de Oliveira 2005-12-01 19:00:10 UTC
Why do you say that this is a bug of the website, if EVERY other browser that i tried works?

tested on: firefox, opera, lynx, links, internet explorer and even dillo.

I dont think you shouldnt close the bugs like this if they arent fixed... but ok, do as you wish. its a bug of the site then...
Comment 3 Thiago Macieira 2005-12-01 19:27:11 UTC
Repeating: it's a bug of the website. ALL the other browsers you tried are doing it wrong: they ignore the Content-Location header.

They shouldn't.

Standards exist for a reason.

Please do not reopen. This bug will not be "fixed" (because it is not a bug).

*** This bug has been marked as a duplicate of 82747 ***
Comment 4 Pedro de Oliveira 2005-12-01 19:29:20 UTC
Well from what i've been reading the Content-Location should only be used when the server returns codes 301 or 302 (temporary or permanent redirect). If its a 200 it should be the http redirect that is on the HEAD.

Maybe you should take a look at the HTTP RFC before answering, but if you want to have it closed, then do it!

ITs the project that loses.
Comment 5 Pedro de Oliveira 2005-12-01 19:34:15 UTC
One more thing http://suika.fam.cx/~wakaba/-temp/wiki/wiki?Content-Location
Comment 6 Pedro de Oliveira 2005-12-01 19:47:16 UTC
Sorry but im going to open just one more time, for you to take a look at what i said. After you read it and answer me i will not reopen it again. 
Thanks
Comment 7 Thiago Macieira 2005-12-01 19:52:58 UTC
Quoting from RFC 2616, section 14.14 Content-Location:

"The value of Content-Location also defines the base URI for the entity."

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.14

Konqueror honours that behaviour. The other browsers don't.

Closing for the third time. We've been through this for the other bug reports. I know what I'm talking about.

One last thing: do not reopen bug reports when you've been told not to. We read everything people write and I would have replied to your comment even if you had not reopened.

*** This bug has been marked as a duplicate of 82747 ***