After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600826 - False rewritten URL
False rewritten URL
Status: RESOLVED DUPLICATE of bug 598277
Product: libsoup
Classification: Core
Component: HTTP Transport
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2009-11-05 14:43 UTC by Reinout van Schouwen
Modified: 2009-11-21 23:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
"epiphany -p https://intranet.huygensinstituut.knaw.nl/weblog/" without Privoxy (11.37 KB, text/plain)
2009-11-06 09:56 UTC, Reinout van Schouwen
Details

Description Reinout van Schouwen 2009-11-05 14:43:50 UTC
When I visit https://intranet.huygensinstituut.knaw.nl/ (might be firewalled from outside...) Epiphany/Webkit rewrites the URL to https://intranet.huygensinstituut.knaw.nl//intranet.huygensinstituut.knaw.nl/weblog/ and the page obviously fails to load and the server gives a 404.

Any hints on how to debug this?
Comment 1 Gustavo Noronha (kov) 2009-11-05 16:05:09 UTC
Could you please run Epiphany with WEBKIT_DEBUG=network in your environment, and go to that site? Be sure to give epiphany the -p option in case you already have other windows open. Neither Epiphany nor WebKitGTK+ perform URL rewrites such as the one you described, so I am betting your server is forcing a redirect in a way someone is not interpreting correctly. Might be a bug in either webkit or libsoup.
Comment 2 Reinout van Schouwen 2009-11-05 16:42:49 UTC
I get it now. It's yet another side effect of using Privoxy. With a direct connection, it works. Moving to libsoup.

$ WEBKIT_DEBUG=network epiphany -p https://intranet.huygensinstituut.knaw.nl/weblog/

** (epiphany:8808): WARNING **: WEBKIT_DEBUG is not empty, but this is a release build. Notice that many log messages will only appear in a debug build.
> CONNECT intranet.huygensinstituut.knaw.nl:443 HTTP/1.1
> Soup-Debug-Timestamp: 1257439018
> Soup-Debug: SoupSessionAsync 1 (0x13bd000), SoupMessage 1 (0x15a48c0), SoupSocket 1 (0x23654d0)
> Host: intranet.huygensinstituut.knaw.nl
  
< HTTP/1.0 200 Connection established
< Soup-Debug-Timestamp: 1257439018
< Soup-Debug: SoupMessage 1 (0x15a48c0)
< Proxy-Agent: Privoxy/3.0.15
< 
  
> GET /weblog/ HTTP/1.1
> Soup-Debug-Timestamp: 1257439018
> Soup-Debug: SoupSessionAsync 1 (0x13bd000), SoupMessage 2 (0x15a4a40), SoupSocket 1 (0x23654d0)
> Host: intranet.huygensinstituut.knaw.nl
> User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl-nl) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+
> Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
> Accept-Encoding: identity
  
< HTTP/1.1 301 Moved Permanently
< Soup-Debug-Timestamp: 1257439019
< Soup-Debug: SoupMessage 2 (0x15a4a40)
< Date: Thu, 05 Nov 2009 16:36:52 GMT
< Server: Apache
< X-Powered-By: PHP/4.3.9
< X-Pingback: https://intranet.huygensinstituut.knaw.nl/weblog/xmlrpc.php
< Location: https://intranet.huygensinstituut.knaw.nl//intranet.huygensinstituut.knaw.nl/weblog/
< Content-Length: 0
< Connection: close
< Content-Type: text/html; charset="UTF-8"
  
> CONNECT intranet.huygensinstituut.knaw.nl:443 HTTP/1.1
> Soup-Debug-Timestamp: 1257439019
> Soup-Debug: SoupSessionAsync 1 (0x13bd000), SoupMessage 3 (0x15a4d40), SoupSocket 2 (0x23654d0)
> Host: intranet.huygensinstituut.knaw.nl
  
< HTTP/1.0 200 Connection established
< Soup-Debug-Timestamp: 1257439019
< Soup-Debug: SoupMessage 3 (0x15a4d40)
< Proxy-Agent: Privoxy/3.0.15
< 
  
> GET //intranet.huygensinstituut.knaw.nl/weblog/ HTTP/1.1
> Soup-Debug-Timestamp: 1257439019
> Soup-Debug: SoupSessionAsync 1 (0x13bd000), SoupMessage 2 (0x15a4a40), SoupSocket 2 (0x23654d0), restarted
> Host: intranet.huygensinstituut.knaw.nl
> User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl-nl) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+
> Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
> Accept-Encoding: identity
  
< HTTP/1.1 404 Not Found
< Soup-Debug-Timestamp: 1257439019
< Soup-Debug: SoupMessage 2 (0x15a4a40)
< Date: Thu, 05 Nov 2009 16:36:52 GMT
< Server: Apache
< Content-Length: 240
< Connection: close
< Content-Type: text/html; charset="iso-8859-1"
Comment 3 Dan Winship 2009-11-05 17:10:56 UTC
how is this libsoup's fault? it looks like the server (or privoxy) is sending back a bad Location header?
Comment 4 Reinout van Schouwen 2009-11-06 09:28:26 UTC
@Dan, because libsoup has known problems with proxies I assumed this would be another instance. All I know is that the problem doesn't occur with Gecko, with or without Privoxy, and does occur with Epiphany/Webkit if Privoxy is enabled.
Comment 5 Reinout van Schouwen 2009-11-06 09:55:09 UTC
I have some more data: this problem only occurs when loading the URL with https:// ; in that case a permanent redirect is given, apparently pointing to the wrong URL. I'm beginning to think this is actually a server misconfiguration of some kind. When I try visiting the https URL with Firefox (with or without Privoxy), the redirect isn't followed either but I end up on the original (pre-redirect) page instead. This is also what happens when loading the URL with Epiphany/Webkit *without* Privoxy (see upcoming debug log). Only *with* Privoxy and https, Epiphany gets the faulty(?) redirect.
Comment 6 Reinout van Schouwen 2009-11-06 09:56:34 UTC
Created attachment 147085 [details]
"epiphany -p https://intranet.huygensinstituut.knaw.nl/weblog/" without Privoxy
Comment 7 Dan Winship 2009-11-21 23:08:54 UTC
fixed in git, will be in libsoup 2.28.2

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