On Wed, Mar 11, 2015 at 07:24:17PM -0400, dominus.ceo wrote:
Hi there,
> Actually already did that, and i got the next answere:
>
> [root@proxy-n1 ~]# curl -H "Auth-Method: plain" \
> > -H "Auth-User: ricardo.carrillo" \
> > -H "Auth-Pass: r3dh4t" \
> > -H "Auth-Protocol: imap" \
> > -H "Auth-Login-Attempt: 1" \
> > -i http://192.168.122.170:80/correo-proxy-auth/index.php
> HTTP/1.1 500 Internal Server Error
> Server: nginx/1.6.2
> Date: Wed, 11 Mar 2015 23:18:54 GMT
> Content-Type: text/html
> Transfer-Encoding: chunked
> Connection: keep-alive
> X-Powered-By: PHP/5.4.16
>
> but the error logs are not very descriptive.
That says that nginx is sending the request to php, which is a good start.
Temporarily replace the index.php file with one which just does
print_r($_SERVER)
and see what it shows when you make the same manual request. Your
objective is to see that the nginx/php integration is working.
If that request does give a sensible response, then you will want to
look more closely at your original index.php. If it does not give a
sensible response, then look more closely at what nginx sends to the php
(fastcgi) server.
f
--
Francis Daly francis@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx