comment on

I don't think you can access ASP session data from anywhere other than an ASP within that application. You can't even share the data between websites on the same IIS server.

You could iterate through the Session collection, and save the data to disk or database before passing the user to the apache site. And just pass them over with a unique id that's difficult to guess - perhaps an MD5 hash of some sort. Then in the Apache application, query the database or file and read in the session data to your favorite Apache Session manager.

The problem is that if you pass the user back to the parent application, the Session might have expired by then, forcing the user to log in again. So you might need to increase the Session time in IIS. I would look in to whether it's possible to move your new application to IIS, or the original application to Apache - it might make things easier.

Simon Flack ($code or die)
$,=reverse'"ro_';s,$,\$,;s,$,lc ref sub{},e;$, =~y'_"' ';eval"die";print $_,lc substr$@,0,3;

In reply to Re: Perl Win32 Apache/IIS Session Management by $code or die
in thread Perl Win32 Apache/IIS Session Management by learn_forever

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks