Thanks.
Unfortunately cookies aren't an option for this project. There is concern that some of our users won't have them turned on. So the project parameters require us to use a session file on the server.
The CAD files are of 3D models (large assemblies) and one of the goals of this project is to serve them to our users as quickly as possible. If they are encrypted, they cannot be served as quickly. We currently provide similar access to similar files via a VPN tunnel and it is slow. After weighing all of our options, this is what we've decided to do and this too is a project parameter.
But my question pertains to the use of CGI::Session. If CGI::Session is called via a SSL connection, and the session object is instantiated via that connection, can you later change the connection (i.e. utilizing a non-secure HTTP header) without breaking the session object? Do you have to maintain the HTTPS connection for the object to remain valid?
In reply to Re^2: CGI::Session Question
by Perobl
in thread CGI::Session Question
by Perobl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |