<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Qlik Sense Enterprise returns error 400 Bad request with header authentication when addressed with DNS name in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-returns-error-400-Bad-request-with-header/ta-p/1713346</link>
    <description>&lt;P&gt;Qlik Sense Enterprise returns 400 Bad request errors when accessed using the DNS name and with header authentication implemented.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Qlik Sense&amp;nbsp;Proxy service losgs (Trace/Audit_proxy) read:&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;1923969 20200420T092701.236+0100 WARN QlikServer1 Audit.Proxy.Proxy.Core.Connection.Validation.ConnectionDataValidator 37 2535c7fe-bf18-4abf-932f-06d11772f7f4 DOMAIN\qvservice &lt;STRONG&gt;Http request Host is not allowed: insights.domain.local.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Environments:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Sense Enterprise for Windows November 2019 and later&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Verify that the DNS name is added to the WebSocket origin white list in the virtual proxy.&amp;nbsp;In earlier versions prior to November 2019, this list of allowed host names was only checked against for WebSocket connections. More recent versions also verify it for HTTP connections.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For information on how to configure the WebSocket origin white list, see&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/How-to-configure-the-WebSocket-origin-white-list-and-best/ta-p/1716765" target="_self"&gt;How to configure the WebSocket origin white list and best practices&lt;/A&gt;&amp;nbsp;.&lt;BR /&gt;&lt;BR /&gt;Please also note that the name should be added in the allowlist without the protocol. Such as:&lt;/P&gt;
&lt;P&gt;Correct:&amp;nbsp;&lt;STRONG&gt;insights.domain.local&lt;/STRONG&gt;&lt;BR /&gt;Incorrect:&lt;STRONG&gt; &lt;A href="https://insights.domain.local" target="_blank" rel="noopener"&gt;https://insights.domain.local&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Feb 2022 13:55:35 GMT</pubDate>
    <dc:creator>Damien_V</dc:creator>
    <dc:date>2022-02-17T13:55:35Z</dc:date>
    <item>
      <title>Qlik Sense Enterprise returns error 400 Bad request with header authentication when addressed with DNS name</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-returns-error-400-Bad-request-with-header/ta-p/1713346</link>
      <description>&lt;P&gt;Qlik Sense Enterprise returns 400 Bad request errors when accessed using the DNS name and with header authentication implemented.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Qlik Sense&amp;nbsp;Proxy service losgs (Trace/Audit_proxy) read:&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;1923969 20200420T092701.236+0100 WARN QlikServer1 Audit.Proxy.Proxy.Core.Connection.Validation.ConnectionDataValidator 37 2535c7fe-bf18-4abf-932f-06d11772f7f4 DOMAIN\qvservice &lt;STRONG&gt;Http request Host is not allowed: insights.domain.local.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Environments:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Sense Enterprise for Windows November 2019 and later&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Verify that the DNS name is added to the WebSocket origin white list in the virtual proxy.&amp;nbsp;In earlier versions prior to November 2019, this list of allowed host names was only checked against for WebSocket connections. More recent versions also verify it for HTTP connections.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For information on how to configure the WebSocket origin white list, see&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/How-to-configure-the-WebSocket-origin-white-list-and-best/ta-p/1716765" target="_self"&gt;How to configure the WebSocket origin white list and best practices&lt;/A&gt;&amp;nbsp;.&lt;BR /&gt;&lt;BR /&gt;Please also note that the name should be added in the allowlist without the protocol. Such as:&lt;/P&gt;
&lt;P&gt;Correct:&amp;nbsp;&lt;STRONG&gt;insights.domain.local&lt;/STRONG&gt;&lt;BR /&gt;Incorrect:&lt;STRONG&gt; &lt;A href="https://insights.domain.local" target="_blank" rel="noopener"&gt;https://insights.domain.local&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 13:55:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-returns-error-400-Bad-request-with-header/ta-p/1713346</guid>
      <dc:creator>Damien_V</dc:creator>
      <dc:date>2022-02-17T13:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Enterprise returns error 400 Bad request with header authentication when addressed with DNS name</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-returns-error-400-Bad-request-with-header/tac-p/2162570#M11166</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In Modheader the authentication was success, but in qlik cli&amp;nbsp; am getting Error: 400 - Bad Request - Qlik Sense, I am not sure when&amp;nbsp; the token was same in modheader and qlikcli its giving different ouput for JWT validation&lt;/P&gt;
&lt;P&gt;when migrating from qliksense to cloud.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can i get some hints to trouble shoot the issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jan 2024 19:50:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-returns-error-400-Bad-request-with-header/tac-p/2162570#M11166</guid>
      <dc:creator>Farsana</dc:creator>
      <dc:date>2024-01-17T19:50:39Z</dc:date>
    </item>
  </channel>
</rss>

