B
brianlafertewk
Guest
Peter, I have a question about this fix (I received the fix yesterday and installed in on a dev server last night). Previously in WebSpeed we could use the following and a redirect would be sent: output-http-header ("Status","302"). output-http-header ("Location", " www.progress.com"). After this change, that logic will not work. In order to get the same functionality, the code would need to look like: output-http-header ("","HTTP/1.1 302 Redirect"). output-http-header ("Location", " www.progress.com"). Is this expected? I didn't see any mention of needing to change code in the release notes. FYI: To keep the old functionality a change can be made to cgituils.i (output-http-header) to treat a 'Status' header like the 'HTTP/1.1' header. This does cause you to manage your out custom cgiutil.i and merge any future changes manually. Also, previously if a call to 'set-cookie' was made before the first call to 'output-http-header', Webspeed would somehow handle that. Right now, it appears setting the cookie will cause the HTTP/1.1 200 OK to be sent, and any other 'HTTP/1.1' status sent will cause the server to throw a 500. In this case I'm less concerned as it's mainly older code examples that set the cookie before the header and I see the change as just exposing a poorly formed header that should never have been supported. But it was supported under Classic WebSpeed.
Continue reading...
Continue reading...