Re: 401 Authorization explained
Re: 401 Authorization explained
- Subject: Re: 401 Authorization explained
- From: Johann Werner <email@hidden>
- Date: Tue, 10 Apr 2012 08:49:38 +0200
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.setStatus(401); authRequired.setHeader("Basic realm=\"Videos\"", "WWW-Authenticate"); if (origin != null) authRequired.setHeader(origin, "Access-Control-Allow-Origin"); return authRequired; } else { […] }
Am 07.04.2012 um 19:38 schrieb Klaus Berkling: Is this useful:
It covers how 401 Authorization can be done in Wonder/WebObjects.
kib
"The trouble with normal is it always gets worse." Bruce Cockburn
Web Application Dev. & Systems Analyst
DynEd International, Inc.
www.dyned.com
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden