|
From: | David Woolley |
Subject: | Re: [Lynx-dev] Lynx doesn't follow 30* redirect if the Location is the same |
Date: | Thu, 15 Jan 2015 22:02:19 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 |
On 15/01/15 14:40, Martin Tournoij wrote:
If I do a request: POST /test and this returns a 303 with: Location /test Lynx decides not to redirect to the new /test URL... If I change either the original request or the Location response to include a query parameter (ie. s=t), Lynx redirects as expected. Is this a bug or a feature? All browsers that I tested properly redirect, except for Lynx and derivatives (Links, ELinks).
What was the most recent GET? If the sequence was: GET /test POST /test 303 (Location=/Test) This is allowable, in the absence of conflicting cache-control directives. If the sequence was: GET /trial POST /test 303 (Location=/Test) it is a bug.
[Prev in Thread] | Current Thread | [Next in Thread] |