This issue can be resolved by installing Maintenance Pack 2 (MP2)
for HP-AS (see
http://www.hpmiddleware.com/SaISAPI.dll/SaServletEngine.class/support/patch_
download.jsp).

-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 3:11 PM
To: Slide Users List
Subject: Re: Deploying Slide 1.0.16 on HP Application Server 8.0


> The issue described in the previous message has been resolved by a
> patch for HP-AS.  However, the following exception is generated whenever
two
> or more WebDAV methods are invoked during an HTTP connection to Slide
> deployed on HP-AS:
>
> 15 Jan 2002 12:57:44 - org.apache.slide.webdav.WebdavServlet - ERROR -
> java.lang.IllegalArgumentException: Cookie name Version is a reserved
token
>  [01/15/02 12:57:44][executor-0][E]: Handling error; throwable is "null",
> status code is "500" and message is "No detailed message".
>  [01/15/02 12:57:44][executor-0][E]: Handling error; throwable is "null",
> status code is "500" and message is "No detailed message".
>
> Here is the corresponding stack trace:
>
> java.lang.IllegalArgumentException: Cookie name Version is a reserved
token
>   at javax.servlet.http.Cookie.<init>(Cookie.java:185)
>   at

>
com.hp.mwlabs.j2ee.containers.servlet.http.HttpServletRequestImpl.getUserPri
> ncipal(HttpServletRequestImpl.java:604)
>   at
> org.apache.slide.webdav.WebdavUtils.getSlideToken(WebdavUtils.java:221)
>   at
> org.apache.slide.webdav.method.WebdavMethod.<init>(WebdavMethod.java:241)
>   at

> Any ideas?

Slide is callin getUserPrincipal on the request object (Slide always does
this on each request, and relies on the container provided authentication).
I don't see anything wrong with that from the Slide perspective. The
container appears to be going through a lot of stuff in response to that;
maybe it would need some syncing somewhere.

Remy


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to