> Is there a way to allow an unauthenticated POST request from a > non-interactive client using X509 certificates for authentication to remain > a POST request once it authenticates properly?
It may be possible with some changes to the login Webflow, but you're in uncharted territory. > The 302 redirects of the > request as a function of authentication cause the original request to end up > a GET on the resource. That's simply how the CAS protocol works. Having CAS refrain from redirects is a substantial change to the mechanics of the server; expect some pain points. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
