<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[FrontAccounting forum — Frontaccounting behind reverse proxy?]]></title>
		<link>https://frontaccounting.com/punbb/viewtopic.php?id=5468</link>
		<atom:link href="https://frontaccounting.com/punbb/extern.php?action=feed&amp;tid=5468&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Frontaccounting behind reverse proxy?.]]></description>
		<lastBuildDate>Fri, 30 Jan 2015 07:30:16 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Frontaccounting behind reverse proxy?]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=22355#p22355</link>
			<description><![CDATA[<p>Thanks for the feedback. Sharing is what makes the community dependable and trusted.</p>]]></description>
			<author><![CDATA[null@example.com (apmuthu)]]></author>
			<pubDate>Fri, 30 Jan 2015 07:30:16 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=22355#p22355</guid>
		</item>
		<item>
			<title><![CDATA[Re: Frontaccounting behind reverse proxy?]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=22354#p22354</link>
			<description><![CDATA[<p>Thank you for that pointer! It got me started going in the right direction.</p><p>Ultimately, the problem turned out to be something different: my proxy configuration inserted the X-Frame-Option DENY into the response headers. Removing that line from my nginx configuration solved the issue.</p><p>While I was at it, I also changed the proxy configuration to use HTTP 1.1 instead of 1.0:</p><p>&nbsp; &nbsp; proxy_http_version&nbsp; &nbsp; &nbsp; 1.1;</p><p>Hint for anybody who may try to track down similar problems: the Firefox plugin Live HTTP Headers was invaluable in solving this mystery.</p>]]></description>
			<author><![CDATA[null@example.com (kkeane)]]></author>
			<pubDate>Fri, 30 Jan 2015 07:07:39 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=22354#p22354</guid>
		</item>
		<item>
			<title><![CDATA[Re: Frontaccounting behind reverse proxy?]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=22137#p22137</link>
			<description><![CDATA[<p>Trace the login method that check for IP spoofing and tailor it to suit your needs.</p>]]></description>
			<author><![CDATA[null@example.com (apmuthu)]]></author>
			<pubDate>Mon, 12 Jan 2015 20:29:12 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=22137#p22137</guid>
		</item>
		<item>
			<title><![CDATA[Frontaccounting behind reverse proxy?]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=22130#p22130</link>
			<description><![CDATA[<p>I am using Frontaccounting 2.3.22. Works beautifully when I access the Web server directly.</p><p>I would like to use it behind a reverse proxy (nginx). This seems to work partially, but AJAX calls seem to time out instead of succeed.</p><p>Is there any information about how to make such a setup work?</p><p>Here is the relevant part of my nginx.conf:</p><div class="codebox"><pre><code>  location /accounting {
    proxy_pass https://&lt;myinternalserver&gt;:443/accounting;
    proxy_set_header        X-Real-IP       $remote_addr;
    proxy_set_header        Host            $host;
    proxy_redirect          off;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_connect_timeout 90;
    proxy_send_timeout 90;
    proxy_read_timeout 90;
    client_max_body_size 8m;
    client_body_buffer_size 128k;
    proxy_buffering off;
    add_header X-Frame-Options DENY;
  }</code></pre></div>]]></description>
			<author><![CDATA[null@example.com (kkeane)]]></author>
			<pubDate>Sun, 11 Jan 2015 21:21:38 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=22130#p22130</guid>
		</item>
	</channel>
</rss>
