While red tape is uncool, we're stuck with the current state of affairs. One strategy is printing set-cookie headers, like this:

Of course, this does absolutely nothing in the way of fine details like escaping values, etc. (The CGI module does all of this automatically when used correctly.) Escaping variable names is particularly unstable: I've seen cases where different versions of IE/NS had different ideas about whether to stomp underscores in variable names before sending them.

Another idea to consider is a very minimal use of the CGI module. That is: refactor the acquisition of variable/cookie names and values, and use print $q->header and its variants, and $VarName = $q->cookie(...) to properly construct the cookies...but leave all generation of HTML proper as-is (print to STDOUT is typical). I personally am accustomed to editing HTML in a programming file editor rather than a GUI environment, so I have no immediate pressure to use any of the HTML-generating shortcuts.

Makeshifts last the longest.

Well, I solved the issue today at work, one problem was that I realised I had the wrong day of the week listed for the date/year combo in the expires list.

Another step I took was to remove the arbitrary &print_headers call that occurred at the beginning of the script and place it within subs that would require a header to print

Then I had to play with the path a bit...I don't have admin rights...am a systems engineer doing software engineering for my boss as a "freebie"..as a result my code is outside of the cgi-bin and my paths are all over the damn place until the program goes prime time..thus the path=/ option had to be massaged a bit ...

TexasTess
"Great Spirits Often Encounter Violent Opposition From Mediocre Minds" --Einstein

-Blake

I'll have to check..it's 5.something...and it might have been "installed" but it wasn't functional...don't ask why..I don't have admin rights on the server all I know is it didn't work...then all of a sudden it appeared after I cried enough..and it started working :-)