Let's not forget about HTTPS, and as far as calling out that a specific HTTP request method (POST) can you explain further your rationale?<br><br><div class="gmail_quote">On Sat, Mar 21, 2009 at 5:56 AM, Floren Munteanu <span dir="ltr"><<a href="mailto:nginx@yqed.com">nginx@yqed.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
<br>
> If what you *really* want is a web interface to manage the users, simply<br>
make (or pay someone to make) a web interface to manage the password files. <br>
Problem solved, no waiting for asynchronous mysql interface.<br>
<br>
</div>That is not a viable solution, you know it. Managing sensitive files in a<br>
web environment is very unsecure, through a web interface. Ya, you can<br>
create a htpasswd file into /etc/nginx dir for example and do a chmod<br>
0700/chown nginx on it. Then, it is secure to stick in there your<br>
usernames/passwords. But to use PHP or other language to manipulate<br>
sensitive data through a POST that can get sniffed easy by anyone is simply<br>
insane, IMO. Not to mention that your file has to be editable by anyone in<br>
order to have your script write information into it...<br>
<br>
<br>
<br>
<br>
</blockquote></div><br>