Re^2: Authorization HTTP header isn't coming through

Which means for me, I need to separate authentication into its own piece of code and call it from Apache as an AuthHandler, right.

Thanks!

Comment on Re^2: Authorization HTTP header isn't coming through - why?

Replies are listed 'Best First'.
Re^3: Authorization HTTP header isn't coming through - why? by ikegami (Patriarch) on Aug 23, 2010 at 19:14 UTC
Or you could use form-based authentication.	[reply]
Re^4: Authorization HTTP header isn't coming through - why? by isync (Hermit) on Aug 23, 2010 at 19:18 UTC
That would solve the data-sharing problems (see below) but isn't feasible in a scenario which relies on standards like Basic/Digest HTTP auth. For example, you can't teach a WebDAV client to process a login-scheme I define.	[reply]