4 messages in ru.sysoev.nginxRe: nginx front-end to sharepoint| From | Sent On | Attachments |
|---|---|---|
| ngin...@public.gmane.org | Feb 28, 2008 12:16 pm | |
| Igor Sysoev | Feb 28, 2008 12:29 pm | |
| ngin...@public.gmane.org | Feb 28, 2008 1:17 pm | |
| Igor Sysoev | Feb 29, 2008 8:28 am |
| Subject: | Re: nginx front-end to sharepoint | |
|---|---|---|
| From: | Igor Sysoev (is-G...@public.gmane.org) | |
| Date: | Feb 29, 2008 8:28:59 am | |
| List: | ru.sysoev.nginx | |
On Thu, Feb 28, 2008 at 04:18:16PM -0500,
ngin...@public.gmane.org wrote:
Yes, we are using Basic authentication.
Have no idea. Could create debug log with dummy username/password ?
Igor Sysoev wrote:
On Thu, Feb 28, 2008 at 03:17:07PM -0500,
ngin...@public.gmane.org wrote:
I am attempting to replace squid 3.0 with nginx as a reverse proxy to a sharepoint server with SSL and user-authentication. The problem I am having is nginx does not appear to pass the credentials to the real server w/o modifying them (after several failed attempts, once simply gets access denied). I am able to accomplish this in squid with this option: login=PASS
nginx should pass all headers as is. Do you use Basic authentication ?
I'm wondering if anybody has any insight/experience into this issue. I have included the relevant portions of my nginx.conf and my old squid.conf. Any help would be greatly appreciated.
Thank you.
nginx.conf:
http { server { listen 443; server_name 192.168.0.10;
ssl on; ssl_certificate /conf/nginx/cert.pem; ssl_certificate_key /conf/nginx/key.pem;
location / { proxy_pass https://192.168.0.1/; } } }
squid.conf:
https_port 443 cert=/conf/squid/cert.pem key=/conf/squid/key.pem \ cafile=/conf/squid/ca.pem vhost cache_peer 192.168.0.1 parent 443 0 login=PASS no-query ssl proxy-only \ originserver sslflags=DONT_VERIFY_PEER,DONT_VERIFY_DOMAIN
-- Igor Sysoev http://sysoev.ru/en/