cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HTTP 400 Bad Request for users

AHassan
MEGA Partner
MEGA Partner

I hope this post will help others to overcome this known issue which users may face when they try to login HOPEX.

Scenario:
Single Sign On (SSO) enabled
HOPEX V4 – V5

When users try to connect to HOPEX they get the below error – not all users are getting this error only some users will face this issue.

 

AHassan_0-1661946132017.png

 

This is not a HOPEX issue but a generic known issue where Microsoft has provided a solutions for this - according to Microsoft “this issue may occur if the user is a member of many Active Directory user groups”.

https://docs.microsoft.com/en-us/troubleshoot/developer/webapps/iis/www-administration-management/ht...

Solution: increase the size of the header on the server hosting HOPEX, by Setting "MaxFieldLength" and "MaxRequestBytes" registry entries.

 

Registry keys are located at the following sub key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

 

Possible values:

AHassan_0-1661946375942.png

 

After setting the above values:

  • Close the registry editor and open the command prompt under the administrator context (i.e. right-click, run as administrator)
  • Type the following command: net stop http
  • Hit Enter and wait for the command to finish processing
  • Type the following command: net start http 
  • Hit Enter and wait for the command to finish processing
  • Type the following command: iisreset
  • Hit Enter and wait for the command to finish processing
  • Test again. IIS should now allow for a larger header in the request.

Important:
Changing these registry keys should be considered to be extremely dangerous – please set some realistic values to avoid any unwanted impact.

 

1 Reply

oguimard
Retired

Thanks for the sharing.

 

Moreover cleaning browser historical data can solve some cases.