Reply to thread

Message

<blockquote data-quote="2102Michael" data-source="post: 929053" data-attributes="member: 109233">It was an firewall issue. This is the information I got from my firewall specialist:&nbsp;&nbsp;http-status 417 indicates a HTTP/1.1 request-header (Expect: 100-continue) when doing a POST, which is not supported by Squid-proxy.&nbsp;You can configure squid to ignore this request-header, the client will fallback without even noticing it.&nbsp;Just add this line to your squid.conf:&nbsp;ignore_expect_100 onSo the problem is solved now <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> - thank you for your support! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" /></blockquote>

[QUOTE="2102Michael, post: 929053, member: 109233"] It was an firewall issue. This is the information I got from my firewall specialist: http-status 417 indicates a HTTP/1.1 request-header (Expect: 100-continue) when doing a POST, which is not supported by Squid-proxy. You can configure squid to ignore this request-header, the client will fallback without even noticing it. Just add this line to your squid.conf: ignore_expect_100 on So the problem is solved now :) - thank you for your support! (y) [/QUOTE]

Verification