Re: FastCGI protocol and http headers
"Jason P Sage" <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Organization | Jegas |
| Message-ID | <001801c6b0ed$2c40a690$7e4c8447@dev01> |
-----Original Message----- From: fastcgi-developers-bounces+jasonpsage=jegas.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org [mailto:fastcgi-developers-bounces+jasonpsage=jegas.com-xGejAJT2w6xVgU18Zptdi8XXUOn6P5/[email protected]] On Behalf Of jancha Sent: Wednesday, July 26, 2006 4:39 PM To: fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org Subject: Re: [FASTCGI] FastCGI protocol and http headers Hiello. And where is the problem? Typically what you send back to client is: =========== header1 header2 .... ... [blank new line] and the data =========== So, to send e.g. 403 status, form your answer as simple as: =========== Status: 403 =========== or =========== Content-Type: text/html [blank new line] <html> ... ... =========== hmm... [Jason Peter Sage] Wow... is it really that simple? My headers look a little more complex, and have things cookies, whether or not the cookies are secure or not, GMT (Greenwich Mean Time) Time Stamps, a Tag that is simply called Server: which normally has apache or something in there - and using non parsed headers you say what ever you want... like "HI MOM", you can set time limits on how long your cookies should last. I didn't KNOW I could strip all that stuff out (except I knew cookies were optional). [Jason Peter Sage] You gave a much more straight forward answer than I did and that is a good thing. The status for the Re direct has a little more than Status... but its almost as easy as the PHP REDIRECT command is to type it in. Jason P Sage ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/