3

Right now, if a request length is large, I get either "URI is too large >8192" or "Header is too large >8192"

KunalG
  • 61
  • 8
  • Possible duplicate of [Dropwizard: How to fix 414 Request-URI Too Long](http://stackoverflow.com/questions/27950281/dropwizard-how-to-fix-414-request-uri-too-long) – Joakim Erdfelt May 04 '16 at 16:26
  • See also: http://stackoverflow.com/questions/19549163/set-maximum-url-length-in-jetty – Joakim Erdfelt May 04 '16 at 16:27
  • @JoakimErdfelt both these are about URI size, but not about header size – Petr Kozelka Oct 25 '18 at 11:21
  • 1
    There's no difference in configuration, same configuration impacts both errors you reported. – Joakim Erdfelt Oct 25 '18 at 12:22
  • @JoakimErdfelt You made my day! I didn't bother to check the queries which resulted in "URI is too large" after solving "Header is too large" with that config entry. And if I hadn't read your comment, I probably would have wondered why they disappeared "magically". :-) – YetiCGN Jan 20 '22 at 14:35

0 Answers0