SeAT - forum: Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long - Page 1

Some users doing additional character linking get the following error “Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long” I am still trying to figure out how it’s being triggered, but I am thinking it’s happening when the person has a lot of characters to link. I’ll provide more details as I get them, not seeing anything in logs unfortunately.

I think it can happen if you request too many scopes or something like that. It shouldn’t happen with seat though, even if you select all scopes

If you go back to seat and select link again the account you tried to log in should be up with the characters, if you needed a workaround in the meantime

In the dev page for the app on eve online I think I selected a lot of scopes and same in seat

I was unsure the specific scopes needed

I could probably clean that up a little

Is there a property somewhere that could expand the header size

Or is it on the eveonline side

I’m using my own proxy (nginx)

And cloudflare

The error is on ccps side

:/

Any idea of its the amount of allowed scopes on the ccp dev app side or the amount of requested scopes from the eveseat single sign-on side of things?

It complains about the request being too long, so client side

yea but which side is generating the header with scopes in it

I eventually am going to dig down into the oauth flow that CCP is using, but wanted to see which side I need to trim for now until I can get some time to research

the browser sends the request, so seat

All scopes,

I still have not gotten to debug yet, but is it cause because of the amount of scope along with the large amount of charcters attempting to be linked by one person?

Just know cloudflare is useless if someone can connect right to your backend.. make sure to use mTLS or whitelist only cf ranges..

its https

Doesn't mean anything security wise if you aren't using cloudflare correctly..

I have firewall and only port 443 open and strict full ssl turned on

and proxy on cloudflare

anything else I am missing?

Yeah but is your firewall only allowing cloudflare ranges..?

https://www.cloudflare.com/ips/

I have some other stuff I run through non cloudflare that I need

and they are not static IP's I can whitelist

I might be able to whitelist, ill look into it

anyways, any things I should look at when I get the user to screenshare and see the flow thats triggering this error

ill be tailing the log while they do it, but I didn't see anything out right when I tried to scan through it

Eh just asking.. lots of people rely on Cloudflare but they don't actually secure it properly.. then it becomes, an attacker can cause havoc if they can just bypass Cloudflare directly, There is methods to figure out what the host is if you really want to actually find it..

Which stuff..?

Here is the target URL when it fails. I have to split this into two chats.

https://login.eveonline.com/account/logon?ReturnUrl=%2Fv2%2Foauth%2Fauthorize%3Fclient_id%3DHIDDEN%26redirect_uri%3Dhttps%253A%252F%252FHIDDEN%252Fauth%252Feve%252Fcallback%26scope%3DpublicData%2Besi-alliances.read_contacts.v1%2Besi-assets.read_assets.v1%2Besi-assets.read_corporation_assets.v1%2Besi-bookmarks.read_character_bookmarks.v1%2Besi-bookmarks.read_corporation_bookmarks.v1%2Besi-calendar.read_calendar_events.v1%2Besi-characters.read_agents_research.v1%2Besi-characters.read_blueprints.v1%2Besi-characters.read_chat_channels.v1%2Besi-characters.read_contacts.v1%2Besi-characters.read_corporation_roles.v1%2Besi-characters.read_fatigue.v1%2Besi-characters.read_fw_stats.v1%2Besi-characters.read_loyalty.v1%2Besi-characters.read_medals.v1%2Besi-characters.read_notifications.v1%2Besi-characters.read_opportunities.v1%2Besi-characters.read_standings.v1%2Besi-characters.read_titles.v1%2Besi-characterstats.read.v1%2Besi-clones.read_clones.v1%2Besi-clones.read_implants.v1%2Besi-contracts.read_character_contracts.v1%2Besi-contracts.read_corporation_contracts.v1%2Besi-corporations.read_blueprints.v1

%2Besi-corporations.readcontacts.v1%2Besi-corporations.readcontainerlogs.v1%2Besi-corporations.readcorporationmembership.v1%2Besi-corporations.readdivisions.v1%2Besi-corporations.readfacilities.v1%2Besi-corporations.readfwstats.v1%2Besi-corporations.readmedals.v1%2Besi-corporations.readstandings.v1%2Besi-corporations.readstarbases.v1%2Besi-corporations.readstructures.v1%2Besi-corporations.readtitles.v1%2Besi-corporations.trackmembers.v1%2Besi-fittings.readfittings.v1%2Besi-fleets.readfleet.v1%2Besi-industry.readcharacterjobs.v1%2Besi-industry.readcharactermining.v1%2Besi-industry.readcorporationjobs.v1%2Besi-industry.readcorporationmining.v1%2Besi-killmails.readcorporationkillmails.v1%2Besi-killmails.readkillmails.v1%2Besi-location.readlocation.v1%2Besi-location.readonline.v1%2Besi-location.readshiptype.v1%2Besi-mail.readmail.v1%2Besi-markets.readcharacterorders.v1%2Besi-markets.readcorporationorders.v1%2Besi-markets.structuremarkets.v1%2Besi-planets.manageplanets.v1%2Besi-planets.readcustomsoffices.v1%2Besi-search.searchstructures.v1%2Besi-skills.readskillqueue.v1%2Besi-skills.readskills.v1%2Besi-universe.readstructures.v1%2Besi-wallet.readcharacterwallet.v1%2Besi-wallet.readcorporationwallets.v1%26responsetype%3Dcode%26state%3DHIDDEN

Our Seat is having the same exact issue too!

Seems other tools similar to SeAT are also having similar issues. Ccp likely changed something in the SSO

Let me know if you figure it out

Any one figure this out

The error cleared for us after ccp got their api fixed

I’m still having issues with people that have more than seven characters

I’m not sure if it’s seven is is the only one with errors

IM having this issue with 2 characters

im having this issue with 2 users. im clear installed SEAT today, and try to link character. from first eve acc all ok, from second this error. may be workaround?

I had to wait several hours. And it seemed to resolve itself. Issue with eve I think

what I tell people when this happens (and it always happens randomly) 1. If you are already logged in on the eve website, log out 2. If you are logged out on the eve website, login 3. Try again

It has something to do with Ccp appending headers to the request as it gets redirected. But can never figure out why the redirect happens "some times"

but the 3 above steps have a 100% cure rate

https://github.com/esi/esi-issues/issues/267

right, but it doesnt explain why its random

This is true.. And I cant find the sso-issues issue for it... But that is the problem that is presenting here

yea