----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Hmm,
about that code snippet... why not include a disclaimer in the standard mailing list
header (code excerpts fall under license, see... bla..).. I mean... what's the point
in discussing code, without seeing it... I had the reinstall JServ, this time with
the sources, just to see what you were talking about... first backing-up the
configuration, installing over the existing one, restore the back-up... browse to
find the method mentioned... you could have made my life easier, you know :(
Brings me to an earlier remark I put aside up to now : with all these landmines like
'check the ***** first', you also might forget that the actual faq/bug lists are not
that user friendly, in fact they are not a very good servlet showcase, now are
they... not to mention the list archives... it is not unlikely people don't find
what they need, good intentions or not... no reason to have a go at them... check
your fire...
e-gret,
Danny
jon * wrote:
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> on 2/11/00 3:30 PM, Danny Martens <[EMAIL PROTECTED]> wrote:
>
> > I don't have the 2.0 specs anymore to see what they say about this, to see how
> > this relates to JSERV... could you look this up ? But assuming the spec is
> > identical on that part, take a look at the JSERV source : it just tries to
> > detect an absolute path (based on the hostname), without restoring the
> > absolute
> > path in case of a relative path... in our case that results in no modification
> > whatsoever... and a mystery solved... now wait and see what the servlet API
> > 2.0
> > specs say...
>
> sendRedirect() needs the url to be absolute, that is in the 2.0 spec. Also,
> this issue of absoluteness isn't part of the servlet spec, this is part of
> the HTTP spec. The 2.0 spec says nothing about encodeRedirectUrl() making
> the uri absolute....that was added after 2.0.
>
> Since JServ clearly only implements the 2.0 spec, I suggest that you pass in
> absolute URI's. period.
>
> now, having said that, i *was* passing in absolute uri's and still having
> problems with encodeRedirectUrl()...
>
> one thing to check is to see what the value of "hostname" is in the code. in
> my case, it could be a bazillion different hosts because java.apache.org ==
> jakarta.apache.org == xml.apache.org to the servlet engine and that could be
> what was causing the problem.
>
> > --- actual JSERV code ---
>
> Sigh, please don't post code here. Not only are you posting it without a
> license on it, but it just isn't necessary.
>
> -jon
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
