Re: Sending data to browser's URI field via POST

How about a 302 redirect then?

my $rewritten_url = 'http://pss.example.com/23487129378378123';
print "302 Moved\n";
print "Location: $rewritten_url\n";
print "\n"
[download]

Comment on Re: Sending data to browser's URI field via POST Download Code

Replies are listed 'Best First'.
Re^2: Sending data to browser's URI field via POST by jhourcle (Prior) on Mar 12, 2005 at 23:14 UTC
I'd agree on using an HTTP redirect, but not necessarily a 302: Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client You'd want to use a 303 if the browser supports HTTP/1.1, 302 of they support HTTP/1.0, and no status, just the Location: header if it's pre-HTTP/1.0. You may have to change the logic of your program to deal with GET to the rewritten URL differently from a POST to it, to deal with someone being sent there the first time, vs. coming back to it later for an update.	[reply]

Replies are listed 'Best First'.

Re^2: Sending data to browser's URI field via POST
by jhourcle (Prior) on Mar 12, 2005 at 23:14 UTC

I'd agree on using an HTTP redirect, but not necessarily a 302:

Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client

You'd want to use a 303 if the browser supports HTTP/1.1, 302 of they support HTTP/1.0, and no status, just the Location: header if it's pre-HTTP/1.0.

You may have to change the logic of your program to deal with GET to the rewritten URL differently from a POST to it, to deal with someone being sent there the first time, vs. coming back to it later for an update.

[reply]