<?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>topic Re: Bad message 431 in EE app and website</title>
    <link>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560857#M65243</link>
    <description>&lt;P&gt;That sometimes happens. EE website is rather finicky.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Sep 2025 10:01:10 GMT</pubDate>
    <dc:creator>XRaySpeX</dc:creator>
    <dc:date>2025-09-02T10:01:10Z</dc:date>
    <item>
      <title>Bad message 431</title>
      <link>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560848#M65239</link>
      <description>&lt;P&gt;I’m experiencing a persistent issue when attempting to log in to my account via the EE website using Google Chrome. Each time I submit my credentials, I receive the following error:&amp;nbsp;&lt;!-- StartFragment  --&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Bad Message 431&lt;/STRONG&gt;&lt;BR /&gt;Reason: Request Header Fields Too Large&lt;/P&gt;&lt;P&gt;&lt;!-- EndFragment  --&gt;&lt;/P&gt;&lt;P&gt;This occurs even when:&lt;BR /&gt;• Cookies and site data have been cleared&lt;BR /&gt;• Credentials are typed manually (not autofilled)&lt;BR /&gt;• Extensions are disabled&lt;BR /&gt;• Incognito and Guest modes are used&lt;BR /&gt;• A fresh Chrome profile is created&lt;BR /&gt;Notably, the login works perfectly when using Microsoft Edge, which suggests the issue is specific to how Chrome handles request headers on your site.&lt;BR /&gt;Could you please advise whether this is a known compatibility issue, or if there’s a server-side configuration that might be triggering this error in Chrome&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 09:44:49 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560848#M65239</guid>
      <dc:creator>admin50</dc:creator>
      <dc:date>2025-09-02T09:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: Bad message 431</title>
      <link>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560851#M65240</link>
      <description>&lt;P&gt;Try another browser.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 09:48:57 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560851#M65240</guid>
      <dc:creator>XRaySpeX</dc:creator>
      <dc:date>2025-09-02T09:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: Bad message 431</title>
      <link>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560852#M65241</link>
      <description>&lt;P&gt;It seems to work absolutley fine using microsoft edge but not when using chrome&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 09:51:10 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560852#M65241</guid>
      <dc:creator>admin50</dc:creator>
      <dc:date>2025-09-02T09:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: Bad message 431</title>
      <link>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560857#M65243</link>
      <description>&lt;P&gt;That sometimes happens. EE website is rather finicky.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 10:01:10 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/EE-app-and-website/Bad-message-431/m-p/1560857#M65243</guid>
      <dc:creator>XRaySpeX</dc:creator>
      <dc:date>2025-09-02T10:01:10Z</dc:date>
    </item>
  </channel>
</rss>

