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 595348 - epiphany performs a POST when refreshing a view that was obtained with a GET
epiphany performs a POST when refreshing a view that was obtained with a GET
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: Backend
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-16 11:37 UTC by Sam Morris
Modified: 2009-09-26 06:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sam Morris 2009-09-16 11:37:35 UTC
I use a web application that handles editing items by having the client POST to a URL that, when requested, performs the edit. It then redirects the client to the original URL for viewing the item.

If I perform an edit, and press Refresh after being redirected, epiphany does a POST to the redirected-to URL rather than a GET.

With the gecko backend, pressing refresh would have resulted in a GET to the redirected-to URL.

Here's an example.

localhost - - [16/Sep/2009 12:30:17] "GET /view HTTP/1.1" 200 517
 [ now i'll mark the items on the page as read ]
localhost - - [16/Sep/2009 12:30:57] "POST /view/mark_read HTTP/1.1" 302 274
 [ the response redirects the client ]
localhost - - [16/Sep/2009 12:30:58] "GET /view HTTP/1.1" 200 517
 [ fine so far, now I'm back to the view page. I'll now hit refresh ]
localhost - - [16/Sep/2009 12:31:35] "POST /view HTTP/1.1" 404 226
 [ ouch!]

The two problems that are, I guess, related are:

 1. The final request shoudl have been a GET
 2. I was not prompted for confirmation for resumbitting the POSTed information

This happens with epiphany 2.7.92 and webkit 1.1.14. It does not hapen with epiphany 2.26.3 and xulrunner 1.9.0.14.
Comment 1 Xan Lopez 2009-09-26 06:19:21 UTC
Thanks for the bug report. This looks pretty bad, but I think it's a WebKitGTK+ bug, so I've forwarded it to https://bugs.webkit.org/show_bug.cgi?id=29761. Feel free to CC there if you want to follow the progress, I'm closing this one as NOTGNOME.