RE: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received

2003-03-26 Thread Rene Kluwen
: woensdag 26 maart 2003 0:34 To: Rene Kluwen Cc: Bruno David Rodrigues; [EMAIL PROTECTED] Subject: Re: [Kannel 010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received Rene Kluwen wrote: > > I think you answered your question yourself :). >

Re: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received

2003-03-26 Thread Stipe Tolj
Rene Kluwen wrote: > > I think you answered your question yourself :). > Yes, the querystring should be included in subsequent requests. By intuition I'd disagree. But maybe we should check if other common HTTP clients do this. Should be easy to check. Can someone do this? I'm busy with applying

Re: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received

2003-03-26 Thread Stipe Tolj
Bruno David Rodrigues wrote: > > Imagine this: > original URL: http://foobar/foo?phone=%p&text=%a > Location header: http://barfoo/bar?foo=true&bar=false > > Which URL should kannel use ? Simply the location ? should it add "phone...%a" > to the second URL (http://barfoobar=false&phone=%p&tex

RE: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received

2003-03-25 Thread Rene Kluwen
: RE: [Kannel 010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received Citando Rene Kluwen <[EMAIL PROTECTED]>: > About 302 (temporary) redirecting responses: > > After a GET request, the client (kannel) should redirect the SAME reque

RE: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received

2003-03-25 Thread Bruno David Rodrigues
Citando Rene Kluwen <[EMAIL PROTECTED]>: > About 302 (temporary) redirecting responses: > > After a GET request, the client (kannel) should redirect the SAME request > to the URL pointed to in the Location: header. > This means, the query string should not re-urlencoded. Section 3.2.2 says that