[Catalyst] HTTP redirect - delayed Firefox

[Andy Grundman]

On Feb 8, 2007, at 4:59 PM, Svilen Ivanov wrote:

> 2007/2/8, John Napiorkowski <jjn1056 at yahoo.com>:
> [...]
>>
>> I believe that when redirecting as a result of a post
>> that 303 is supposed to be correct, whereas 302 is
>> used for redirects when the information is merely at a
>> different location.  But I'm not an expert.  So 303 is
>> probably what most of us use redirect for, like when
>> you click on save in a form and then you want to
>> redirect the user back to a different page.
>>
>> I think this is use is because when Firefox sees a 302
>> it's expecting more info or something and it doesn't
>> play nice with the build in server.  It didn't bother
>> me enough to dig.
>
> Thank you John for your prompt answer! I tried 303 - still lags for 5
> seconds when "-k" is on. I can live with this delay as long it doesn't
> appear when I deploy the app on Apache mod_perl/fcgi. Do you know if
> it appears on test server only?

-k is a hack and you shouldn't use it unless you need to do IE  
testing.  Real web servers do not have a problem with keep-alive.   
You may also want to try Catalyst::Engine::HTTP::POE instead. :)