I think my idea would be scenario 4.) I want to: 1.) Open a browser and write Tomcat application's address (localhost:8080/myapp); 2.) Write username and password in login fields of the application; 3.) Save credentials in session after successful login; 4.) Have link to completely separate application on newly opened page; 5.) When link is clicked, request should be sent that contains row: "Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==" Login username and password would be the same for both applications. On this way, I don't need to type username and password again; 6.) >From now on, php application is on-board and Tomcat can be forgotten (it remains reachable only via browser's Back button);
I will look now after httpd that you mentioned, awarnier. Regards awarnier wrote: > > > 4) > User --> front-end --> Tomcat --> Struts application > front-end --> other server --> php application > > If you don't need to be in-between, that is the easiest solution. > As the front-end, you can use many things. Apache httpd being only one > of the possibilities. > > So, which kind of scenario is yours ? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/Basic-authentication-without-a-secure-connection-tp23347310p23359828.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
