https://issues.apache.org/bugzilla/show_bug.cgi?id=52943
--- Comment #3 from Daniel Gruno <dan...@gruno.dk> 2012-03-20 07:35:55 UTC --- The standard way is through REMOTE_USER ( as per http://www.ietf.org/rfc/rfc3875 ) The non-standard way is "meh". If you are referring to modules such as mod_php, mod_lua etc, then it's entirely up to that specific module how it will implement such a feature. Getting down to basics, the browser will, in case of a regular HTTP auth, send an Authorization request header with the username and password encoded in the string. Apache will then pass on the string (inside a table called headers_in) to whichever module, handler, filter, you name it, that wishes to process the requested URL. Some modules will decode the username (and possibly the password), while others will just pass on the encoded string, it's entirely up to them. Having said that; As Nick pointed out, this question is more a question of how CGI and HTTP protocols work than it is how Apache's HTTP Server works, and should probably best be answered in such forums instead. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org For additional commands, e-mail: docs-h...@httpd.apache.org
