One way would be to configure your Domino server to have its FQDN as the public dns hostname, with the internal DNS resolver hardcoded to return the internal IP for that public dns hostname.<div><br></div><div>Regards,</div>
<div>Ray<br><br><div class="gmail_quote">On Thu, Mar 25, 2010 at 7:30 PM, Toni Mueller <span dir="ltr"><<a href="mailto:support-nginx@oeko.net">support-nginx@oeko.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hi,<br>
<br>
I'm running against a wall with this problem:<br>
<br>
I want to have nginx reverse-proxying to a Domino server to access web<br>
mail. The Domino server sets a cookie like this:<br>
<br>
Set-Cookie: LtpaToken=AAECAzRCQUIzOTAzNEJBQjQwMEJDTj1KYW1lcyBULiBLaXJrL09VPUFTREUvTz1BU0NUQUcvQz1ERVfDFlPa9ly73A1MRubC5PW1h4vN; domain=.company.local; path=/<br>
<br>
It is easy to see that all browsers outside of the network where this<br>
name can be resolved, will not accept the cookie, and thus be unable to<br>
log in. I currently have no idea about how to do this.<br>
<br>
What I would like to see is something like<br>
<br>
rewrite_header headername value flags<br>
<br>
(ie, a "natural" extension of the "rewrite" statement). The rewriting<br>
should preferably work in both directions, so one could rewrite request<br>
headers which are going to some backend, as well as response headers.<br>
<br>
Any ideas, please?<br>
<br>
<br>
Kind regards,<br>
--Toni++<br>
<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div><br></div>