geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1747) HTTP-methods checks
Date Tue, 02 Jan 2007 21:33:27 GMT


David Jencks commented on GERONIMO-1747:

HTTP extension methods are supported in jacc-1.1 which is currently (somewhat untestedly)
in 2.0 (trunk).  So, your app should work on 2.0.  I'd be very interested to know if it does

jacc-1.0 does not support http extensions.  You might be able to put the jacc 1.1 jar into
your pre-2.0 server and use the artifact_aliases.xml file to map one to the other, but I don't
recall when the artifact_aliases file appeared and I'm not sure it it works for plain jars.

> HTTP-methods checks
> -------------------
>                 Key: GERONIMO-1747
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: security
>    Affects Versions: 1.0
>         Environment: Windows 2003, java 1.4
>            Reporter: Ilya Platonov
>             Fix For: 1.1.2
>         Attachments: web.xml
> I'm tring to run jakarta-slide web-application on geronimo application server. Slide
provides WebDAV support.
> When security constrain is not set, everything works fine exept some minor issues but
when I put some security constraints for servlets I got following error in server.log.
> 15:43:58,132 ERROR [CoyoteAdapter] An exception or error occurred in the container during
the request processing
> java.lang.IllegalArgumentException: Invalid HTTPMethodSpec
>         at<init>(
>         at<init>(
>         at org.apache.geronimo.tomcat.realm.TomcatGeronimoRealm.hasUserDataPermission(
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
>         at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(
>         at org.apache.geronimo.tomcat.valve.PolicyContextValve.invoke(
>         at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(
>         at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(
>         at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(
>         at org.apache.catalina.core.StandardHostValve.invoke(
>         at org.apache.catalina.valves.ErrorReportValve.invoke(
>         at org.apache.catalina.core.StandardEngineValve.invoke(
>         at org.apache.catalina.valves.AccessLogValve.invoke(
>         at org.apache.catalina.connector.CoyoteAdapter.service(
>         at org.apache.coyote.http11.Http11Processor.process(
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(
>         at
>         at
>         at org.apache.tomcat.util.threads.ThreadPool$
>         at
> When I looked through Geronimo source code I found that "GET", "POST", "PUT", "DELETE",
"HEAD", "OPTIONS" and "TRACE" http-methods hardcoded into HTTPMethodSpec class and if you
tring to  use another method it throws this exception. Problem is that WebDAV specification
extends standard HTTP-methods, for example it uses MKCOL and LOCK methods so jakarta-slide
just not working.
> Is there any workaround for this bug or geronimo is just not able to handle any HTTP
protocol extensions???

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message