Azure Portal: Bad Request - Request Too Long

Question

I just got the following error when I tried to run the built-in b2c editing policy from portal.azure.com . I have 2 portal tabs. Why am I getting this error?

Bad request - request is too long HTTP Error 400. Request header size is too long.

Note. I experienced the same error message while testing the active-directory project -b2c-dotnet-webapp-and-webapi . The reason was that I sent too many cookies. Is this the same problem?

If this is the same problem, should you not delete cookies before creating new ones?

---

I see a lot of cookies for https://login.microsoftonline.com

Answer 1

HTTP Error 400: The header request size is usually too long because there are too many cookies or cookies too large .

Login to Azure AD B2C is through login.microsoftonline.com, like almost all Microsoft services (O365, Azure, etc.). Therefore, if you have several accounts that you have logged in through these services, you accumulate cookies that may cause this problem.

, , Azure , , B2C, B2C .

Azure AD B2C . cookie B2C login.microsoftonline.com. 2019-06-23 . , Azure AD B2C: ,

, , , :

1. . , , , , .

2. , . , http-, cookie Microsoft.

. , : http 400: .

2018-11:

Azure AD B2C b2clogin.com login.microsoftonline.com, , cookie Microsoft.

Answer 2

"HTTP Error 400 Bad Request - Request Too Long" Azure, , URL Microsoft.

Azure. URL: https://account.azure.com/Subscription

"Bad Request Header Too long". URL , : https://account.windowsazure.com/Subscription

Answer 3

cookie. . , , - cookie.

, cookie , login.microsoftonline.com portal.azure.com

Answer 4

, OWIN , MVC, , , ( ) .

, cookie , .

, , .

Answer 5

b2clogin.com, . Microsoft:

• cookie Microsoft.

Answer 6

I got a few answers because I was part of too many active directories. I was part of the active ZERO directories when I came across this problem. I cleared my cookies and took about two steps before this happened again. It seems that the request sent many, many cookies from Microsoft, Azure, Facebook, Google, cookies and AdSense, but deleting them all did not help. Finally, I got access to the incognito tab.

tl; dr Try the incognito tab