I have added authorisation directives to my Apache config, so that the calling of CGI programs requires the entry of profile/password.
Since then I have noticed a change in the server jobs serving CGI (PGM-QZSRCGI). Before the current user profile was QTMHHTP1 for these jobs: this meant that when a user made a request, the server checked to see if there was a job available. If so, it was used, if not it spawned a new one. Hence the problems with persistence of browser 'sessions' (never sure to pick up the same job and in the same state). Since the authorisation change, the server jobs have the current user profile as the profiles of those users that have made requests. That's perfectly understandable and means that the server job is now using the authorisation of the user. What I don't understand is the following 1)I launch the browser 2)Enter my profile & password 3)View page 4)Shut down browser I see that I have a CGI server job with my user profile. Now another user logs in, repeating the above process. It does not re- use `my' server job but spawns another with their profile. This implies a sort of `persistence' that I thought did not exist with the browser. Each time that I re-log back in I am guaranteed to get the same server job? This would have benefits in terms of library list setting, creating objects in QTEMP for reuse etc. And these jobs will remain active until the server is restarted then? Any thoughts would be welcome! ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/u8TY5A/tzNLAA/yQLSAA/wbFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Easy400Group/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
