Re: 401 Authorization explained

2012-04-10 Thread Daniele Corti
Hi 2012/4/10 Chuck Hill > String originalURLFromRequest = request.headerForKey("request_uri"); is it so easy? I thought it was more complicated... Thank you Chuck! On 2012-04-10, at 10:26 AM, Daniele Corti wrote: > > > Hi Everyone, > > I was wondering, if I use the ErrorDocument in Apache fo

Re: 401 Authorization explained

2012-04-10 Thread Chuck Hill
String originalURLFromRequest = request.headerForKey("request_uri"); On 2012-04-10, at 10:26 AM, Daniele Corti wrote: > Hi Everyone, > I was wondering, if I use the ErrorDocument in Apache for the 401 to redirect > on a direct action (for example ErrorDocument 401 > /cgi-bin/WebObjects/wa/req

Re: 401 Authorization explained

2012-04-10 Thread Daniele Corti
Hi Everyone, I was wondering, if I use the ErrorDocument in Apache for the 401 to redirect on a direct action (for example ErrorDocument 401 /cgi-bin/WebObjects/wa/requireLogon ), is there a way in WO to obtain the URI that cause the Authentication Error? In PHP you can use the $_SERVER['REQUEST_UR

Re: 401 Authorization explained

2012-04-09 Thread Johann Werner
Hi Klaus, nice article but you can achieve that with less work (or files). Instead of an "empty" component you could just create an empty response object and return that in your direct action: […] if (noAuthenticationFound) { ERXResponse authRequired = new ERXResponse(); authRequired.setSta

401 Authorization explained

2012-04-07 Thread Klaus Berkling
Is this useful: http://www.berkling.us/theothersite/page1/files/401_authorization_in_wonder.html It covers how 401 Authorization can be done in Wonder/WebObjects. kib "The trouble with normal is it always gets worse." Bruce Cockburn Klaus Berkling Web Application Dev. & Systems Analyst DynEd