EUREKA !!!, to cookie hell and back ... Options

[SirAndy]

alright. i fixed the cookie problem. took me only a few days. i'm tired now ...

ok, here it is in a nutshell:

- cookies are send to the client computer within the HTTP-Header.
- a http-header can NOT be send after any other data has been send to the client. (hence the name HEADER).
- if you attempt to send a cookie AFTER the header was sent, you either (on good systems) get a error message OR the cookie request will be ignored.
- for sloppy/stupid/unexpierienced/stupid/stupid programmers, there is a workaround where you can cache all web-page data in a buffer and if that web-page contains any header/cookie specific calls, those will be collected and send first, then the rest of the page. this is done by the web-server.
- this allows for really shitty code to actually work.
- this is what the guys who made our BBS code were doing. (IBF forums)


so, all i had to do was to set the "i'm a dumb-ass programmer" flag in the server settings,
and voila! it works again ...
Andy

[seanery]

Nothing exciting to see. Our audio guy had the best (panty) shot though. He had to lay on the floor with the boom and had no option but to stare there (IMG:style_emoticons/default/cool.gif)