From: Michael E. <men...@ka...> - 2003-01-13 14:08:51
|
Actually my example of doing https://domain.com -> http://domain.com you can ignore. I remember that this is almost impossible to do with Webware and servlets. I had some funky workaround code I used in Java that allowed me to handle this so I was thinking that I had it working and can't seem to ever remember that I came up with that helper class to do the same functionality... But I'd still love to have forward() working as Luke mentioned. cheers Mike Begin forwarded message: > From: Michael Engelhart <men...@ka...> > Date: Mon Jan 13, 2003 9:04:59 AM US/Eastern > To: "Webware-Devel (E-mail)" <web...@li...> > Subject: Re: [Webware-devel] love hate relationships =) > >> >> Part of the reason why I dont use an external redirect, is so I can >> pass data >> from one servlet to another on a per request basis. For example... >> passing >> error information from my login action to the login page. > > This is a huge thing for me also. I'm not sure if it's only > pertinent for Java Servlet refugees or not but with Java this is a > VERY common way of working. I also find it a very elegant solution to > passing temporary data around and it greatly simplifies the MVC > architechture. > > Another problem I have is that forward() doesn't do something (which I > did with Secure sessions) like forward from > https://domain.com/Login.py > to > http://domain.com/SuccessfulLogin.py > > which I do in almost every web application I build that only needs > username/password encryption. > > Of course you can redirect but you can't stuff a "Welcome message" or > any other data into the request before forwarding it to the non-SSL > page. > > anyway, I'd really, really like to see forward() fixed or working > better. Not sure what I can do to help but if there are a list of > specific "issues" as to why this doesn't work I'd love to see them. > > thanks > Mike > On Sunday, January 12, 2003, at 11:26 PM, Luke Holden (by way of Luke > Holden <lh...@eb...>) wrote: > |
From: Stuart D. <st...@as...> - 2003-01-13 15:51:17
|
Michael Engelhart wrote: > Actually my example of doing https://domain.com -> http://domain.com > you can ignore. I remember that this is almost impossible to do with > Webware and servlets. I had some funky workaround code I used in Java > that allowed me to handle this so I was thinking that I had it working > and can't seem to ever remember that I came up with that helper class > to do the same functionality... > > But I'd still love to have forward() working as Luke mentioned. > > > cheers > Mike Have you tried the Patch that Luke submitted? Does that work for your situation? As time permits, I am working on a solution that integrates that functionality but also works with the absolute paths used with psp-handler and the adapter relative paths used by WebKit. Is it correct to assume that to do what you want, you also need a way to change contexts in the forward? Or do you expect to do everything in the same context? -Stuart- > > Begin forwarded message: > >> From: Michael Engelhart <men...@ka...> >> Date: Mon Jan 13, 2003 9:04:59 AM US/Eastern >> To: "Webware-Devel (E-mail)" <web...@li...> >> Subject: Re: [Webware-devel] love hate relationships =) >> >>> >>> Part of the reason why I dont use an external redirect, is so I can >>> pass data >>> from one servlet to another on a per request basis. For example... >>> passing >>> error information from my login action to the login page. >> >> >> This is a huge thing for me also. I'm not sure if it's only >> pertinent for Java Servlet refugees or not but with Java this is a >> VERY common way of working. I also find it a very elegant solution >> to passing temporary data around and it greatly simplifies the MVC >> architechture. >> >> Another problem I have is that forward() doesn't do something (which >> I did with Secure sessions) like forward from >> https://domain.com/Login.py >> to >> http://domain.com/SuccessfulLogin.py >> >> which I do in almost every web application I build that only needs >> username/password encryption. >> >> Of course you can redirect but you can't stuff a "Welcome message" or >> any other data into the request before forwarding it to the non-SSL >> page. >> >> anyway, I'd really, really like to see forward() fixed or working >> better. Not sure what I can do to help but if there are a list of >> specific "issues" as to why this doesn't work I'd love to see them. >> >> thanks >> Mike >> On Sunday, January 12, 2003, at 11:26 PM, Luke Holden (by way of >> Luke Holden <lh...@eb...>) wrote: >> > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Webware-devel mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-devel > > |
From: Luke H. <lh...@eb...> - 2003-01-13 21:58:47
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 13 January 2003 06:07 am, Michael Engelhart wrote: > But I'd still love to have forward() working as Luke mentioned. See my last two patches at: https://sourceforge.net/tracker/index.php?func=detail&aid=666560&group_id=4866&atid=304866 I dont think the patches cover cross context. I kind of left that for someone with more experiance in dealing with contexts. The first patch allows non reletive urls to work as expected. (ex: 'includeURL("/dir/file")' now works. The second patch is to unwrap a path tries to move up to the parent directory. (siteRoot() returns '../../' etc. Unfortunatly this does not always work as expected. Using includeURL right after a forward() does not work this way for example.) Using these two patches, I am now using includeURL and forward() just like I would in java. I am also using req.arg() and req.setArg() to pass request specific information. (Data set with those methods only live accross requests. So the data dies once the page is finally sent to the user. Much like using the request context in JSP/Java servlets) - -- Luke Holden eBI Solutions Main: (949) 387-5182 Email: lh...@eb... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Iza43q5xXfLZTQkRAkkfAJ9EPO/rAb8blOknJrWj1BjAk/WIUgCgoxcf hqa2sNpC8AKlXDuOzYmr8UI= =M4CZ -----END PGP SIGNATURE----- |