Edmund Lian wrote:

> On 01/13/2003 10:51:09 AM Stuart wrote:
> 
> >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?
> 
> I don't think any solution should be confined to a context. 
> As it stands,
> contexts mean next to nothing application-wise. They're just 
> subdirectories
> off the site root. They way I'd expect (as does Luke) 
> forward, redirect,
> and include to work is:
> 
> URL = "/path/to/target" ---> absolute path to target, starting at site
> root. i.e., "/" = site root and not file system root.
> URL = "path/to/target" ---> relative path to target, starting 
> at servlet's
> directory.
> URL == "../path/../../to/target" ---> relative path to 
> target, normalized
> automatically.

The patch that Luke gave uses siteRoot().  siteRoot() is the root of the
context, not the root URL which is used to dispatch into Webware.  That
would be the adapterName().  Therefore, the behavior that Luke's patch
provides only works in the current Context.

My inclination is to add an optional Context to the includeURL(),
callMethodOfServlet(), and forward() methods that would allow specifying
this.  A Context of None would be interpreted as an absolute reference
relative to DOC_ROOT which is what would be used to access external PSP
pages.  I haven't tried this yet, so I don't know if there are any hidden
gotchas there.

I am currently adding to the Testing context some tests to cover the url
issues we have been discussing.

-Stuart-


-------------------------------------------------------
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
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to