I am putting together a website that has stock HTML pages but it also has pages that are totally generated by a CGI program on the server.

Cookies written on the client by pages generated by the CGI program are not seen by the stock HTML pages.

What is a good way to work around this?

rkwhited

HTML pages aren't capable of doing anything with cookies so you will need to use some other language to handle the cookies - can you post a copy of the bit of code that you don't think is working?

David,

My bad. I am using the javascript/html DOM feature 'document.cookie' ... does that change your reply?

rkwhited

There shouldn't be any problem with javascript accessing the same cookies as a perl/php script etc so long as they are all on the same domain.

I'm not sure what to suggest without seeing the code.

The code is just simple, run of the mill "document.cookie = name + = + value + expires" type code. Same with the read.

But you mention domain. That is where the problem must be. The cgi-bin directory is where the CGI program generates new HTML pages, and the public directory where the static .html pages are located is one directory above the cgi-bin directory.

This fools the browser into thinking it is a different domain evidently ... the cookie code works ok when offline not using the CGI program. But when the code is moved to the server this changes things.

I verified this by reading the cookie directory and the CGI program cookies are written to a different cookie ...

so ... your mention of the domain is a good suspicion ... making the domain the same is looking like the central issue ... and I am not sure that is feasible ...

rkwhited

Ah - I think I may see your problem. Did you remember to set "path=/" in your cookie? if not then it will only be available to the path where the cookie was created.