4 ms·
They're caching the resource based on URI only or on HTTP method and URI only is the problem. If you're caching 400 (which many people have noted is against th
by cestith 7y ago
They're caching the resource based on URI only or on HTTP method and URI only is the problem.
If you're caching 400 (which many people have noted is against the RFC and can be troublesome) then you need to make sure you're only caching it for a matching request. If I send a poisoned header and you cache a 400 for my full request including that poisoned header, then that's one thing. If I send a poisoned header and you cache a 400 for all accesses to that URI whether or not they include the header that caused it to be a bad request, that's vulnerable to this BS.