views:

65

answers:

3

I'm writing a webapp that reponses an HTTP redirect. Is there a way to force the client to forward the headers I include in the response to the new url?

Example request:

POST /insertion HTTP/1.1
Content-Length: 9

(content)

Webapp response:

HTTP/1.x 302 Found
Location: /dock
Mydata: asdf

Next client request:

GET /dock HTTP/1.1
Mydata: asdf

Update: It seems I wasn't clear on the matter. I know cookies would be useful, but I can't use them. Do you know whether exists something like what i'm searching for?

+1  A: 

This is what cookies are used for. You can set it for the browser session and invalidate it after the next request.

Gumbo
+2  A: 

Other than HTTP cookies, there's nothing in the protocol specification about forwarding headers. The client needs to implement this functionality.

Darin Dimitrov
+1  A: 

Put your data in the new url as an argument:

HTTP/1.x 302 Found
Location: /dock?data=asdf

or save it in cookies

HTTP/1.x 302 Found
Location: /dock
Set-Cookie: data=asdf
Iamamac