Re: CGI Session - not creating session file

Do you get a server error? Is there anything of interest in the webserver's log?

If so, it's likely the webserver doesn't have permission to write to that directory.

Also note that using \ backslashes in paths is usually not needed even on windows since / forward slashes work as well and have less issues (for instance; "c:\some\newthing" contains a newline, while "c:/some/newthing" does not)

As an aside, what do you want to accomplish with using perl2exe? There's no real benefit to using it, besides easier distribution to sites that don't have perl installed - and I'm guessing you already have some sort of control over the server you're running this program on.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re: CGI Session - not creating session file

Replies are listed 'Best First'.
Re^2: CGI Session - not creating session file by mwhiting (Beadle) on Aug 03, 2007 at 12:58 UTC
I haven't looked in the servers log, I should do that. I do have full access to this server, but the script will be run on other servers yet that I don't have access to. I tried the backslashes, and as was mentioned, they work fine either way. I did find some issues with using the forward slashes, but those errors come up right away and are easy enough to steer around. Why wouldn't the webserver have permission to write to the system's temp folder? I don't believe this server was set up with any special considerations like that. Also, the folder that the script is in is the d: folder I mentioned, it has 'everybody' permissions on it - what more could a webserver ask for? I want to ask about your comment on perl2exe - how do I make the computer run perl script without having it compiled? I guess I haven't tried the most obvious way - just call it from the URL line - maybe I'll have to associate the extension with NT's Perl & it'll just 'go'. Would it take something else? Michael	[reply]

Replies are listed 'Best First'.

Re^2: CGI Session - not creating session file
by mwhiting (Beadle) on Aug 03, 2007 at 12:58 UTC

I tried the backslashes, and as was mentioned, they work fine either way. I did find some issues with using the forward slashes, but those errors come up right away and are easy enough to steer around.

Why wouldn't the webserver have permission to write to the system's temp folder? I don't believe this server was set up with any special considerations like that. Also, the folder that the script is in is the d: folder I mentioned, it has 'everybody' permissions on it - what more could a webserver ask for? I want to ask about your comment on perl2exe - how do I make the computer run perl script without having it compiled? I guess I haven't tried the most obvious way - just call it from the URL line - maybe I'll have to associate the extension with NT's Perl & it'll just 'go'. Would it take something else?

Michael

[reply]