A Padding To Disable MSIE And Chrome Friendly Error Page [Fix]

Adjusting your server settings can fix this issue

Reading time icon 3 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

a padding to disable msie and chrome friendly error page
Try Opera One, a browser with various functionalities already built-in! A flawless browser like Opera has most functions already under the hood.Here's what's included by default:
  • Easy and intuitive workspace management
  • Ad-blocker mode integrated to load pages faster
  • WhatsApp and Facebook Messenger
  • Customizable Ul and AI-friendly
  • ⇒ Get Opera One

Many users reported that <!– a padding to disable msie and chrome friendly error page –> message prevents them from using certain web apps.

This error means that website or a web app is using padding or extra spaces in the HTTP response headers which prevent it from showing the appropriate response.

In today’s guide, we’re going to solve this problem.

How can I fix a padding to disable MSIE and chrome friendly error page?

Before we start, check if there are any issues with the server, such as downtime. If you’re using Zapier with Slack, this problem will appear if the desired channel isn’t found. If you using AWS, whitelist Grafana dashboards.

1. Clear browser cache

  1. Launch Google Chrome.
  2. Click the three-dots menu icon and select Settings.
    chrome settings menu
  3. On the Settings page, scroll down to the Privacy and Security section.
    privacy and security chrome settings
  4. Click on Clear Browsing Data.
    Clear Browsing Data chrome
  5. Open the Advanced tab, then select a time range. Next, check all the data that you want to clear. Finally, click the Clear Data button and wait for the browsing data to be removed.
    Clear Browsing Data in chrome advanced tab
  6. Close and relaunch the browser and check for improvements.

2. Clear local DNS cache 

  1. Click on the Start menu, type command prompt, and select the option to Run as administrator.
    command prompt search run as administrator
  2. In the Command Prompt, type the following command and hit Enter to execute:
    ipconfig /flushdns
  3. You should see the Successfully flushed the DNS Resolver Cache message when it is completed.
    Successfully flushed the DNS Resolver Cache message in command prompt

3. Change DNS server address

  1. Press the Windows key + R.
  2. Type control and click OK to open Control Panel.
    control run window
  3. Go to Network and choose Network and Sharing Center.
    network and sharing center control panel
  4. From the left pane, click on Change adapter settings.
    Change adapter settings network and sharing center
  5. Right-click on your network adapter and select Properties.
    network properties context menu
  6. In the Properties window, locate and double-click on Internet Protocol Version 4 (TCP/IPv4).
    Internet Protocol Version 4 selected wireless properties window
  7. Under Use the following DNS server addresses option, enter for the Preferred DNS server and Alternate DNS server the two addresses below in that order:
    8.8.8.8
    8.8.4.4

    Use the following DNS server addresses Internet Protocol Version 4 window
  8. Click OK to save the changes.

4. Adjust your AWS configuration

  1. Open your AWS configuration.
  2. Look for the AWSManagedRulesPHPRuleSet rule, it should look like this:
    {
    "Name": "AWS-AWSManagedRulesPHPRuleSet",
    "Priority": 32,
    "Statement": {
    "ManagedRuleGroupStatement": {
    "VendorName": "AWS",
    "Name": "AWSManagedRulesPHPRuleSet"
    }
    },
    "OverrideAction": {
    "None": {}
    },
    "VisibilityConfig": {
    "SampledRequestsEnabled": true,
    "CloudWatchMetricsEnabled": true,
    "MetricName": "AWS-AWSManagedRulesPHPRuleSet"
    }
    }
  3. Remove the rule and check if that solves the problem.

If <!– a padding to disable msie and chrome friendly error page –> message appears on your website, you can go ahead and contact the support to look into this error.

This isn’t the only issue you can encounter and many reported Server error in ‘/’ application as well as Server execution failed messages.

The error is somewhat similar to the Browser sent a request this server could not understand the error that we covered earlier.

Let us know in the comments if you found these helpful solutions to disable MSIE and fix the a padding to disable msie and chrome friendly error page.

More about the topics: Google Chrome Errors

User forum

0 messages