Thanks for you reply Filip,

I am using Glassfish with normal Basic-Authentification and there are no
problems with pages, resources or else. Only this special interaction causes
this issue. Also I wonder about the Status 503, normally the status ist 403
generated by an access denied. 
In my web.xml there are all things permitted for this user (admin):
clipping from web.xml:
         <security-constraint>
        <display-name>SecurityConstraint</display-name>
        <web-resource-collection>
            <web-resource-name>PagesT5</web-resource-name>
            <url-pattern>/*</url-pattern>
            <http-method>POST</http-method>
            <http-method>GET</http-method>               
            <http-method>DELETE</http-method>
            <http-method>HEAD</http-method>
            <http-method>OPTIONS</http-method>
            <http-method>PUT</http-method>
            <http-method>TRACE</http-method>
        </web-resource-collection>
        <auth-constraint>
            <role-name>Guest</role-name>
            <role-name>User</role-name>
            <role-name>HardwareAdmin</role-name>
            <role-name>Admin</role-name>
        </auth-constraint>

Have you or anybody else a hint for me, that shows me the right direction?
Since 2 days I can't  find a solution, a hint or something else. :-(




Filip S. Adamsen-2 wrote:
> 
> Hi,
> 
> This is not a bug in Tapestry, nor is it a problem with Windows - at 
> least I don't have that problem. To be honest I don't even think it's 
> Glassfish's fault, although this works for me with Jetty. Perhaps it's a 
> configuration issue of some sort?
> 
> And no, it's not simple to change the way Tapestry decodes URLs.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/T5.0.13-colon-in-URL-leads-to-503-Error-tp18313019p18316476.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


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

Reply via email to