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 586692 - Non redirection from POST to GET on 301status code
Non redirection from POST to GET on 301status code
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: HTTP Transport
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2009-06-22 21:41 UTC by Christophe Gillette
Modified: 2009-06-22 22:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christophe Gillette 2009-06-22 21:41:17 UTC 
libsoup conforms to the RFC2616 standard by not redirecting a reply from a POST that contains a 301 status code and a valid location (see http://git.gnome.org/cgit/libsoup/commit/?id=325d6c2522b4198a8df342fa3799773a61ccd6dd).

However, all browsers (including WebKit flavors that are not using libsoup) seem to redirect to the given location using a GET and some high traffic web sites are still assuming this behavior (instead of sending a 303 status code). For example, using WebKit with the latest (2.27.2) libsoup version, a user is enabled to access his/her amazon.com account: the browser displays a blank page.
Comment 1 Dan Winship 2009-06-22 22:00:43 UTC 
fixed in git; we were already doing this for 302, i just didn't notice that the spec says that browsers do this for 301 as well