On April 29, 2020 11:16:21 AM UTC, Andrey Repin <anrdaemon@xxxxxxxxxxx> wrote: >Greetings, Ashley Sheridan. >In reply to Your message dated Friday, April 24, 2020, 17:09:19, > > >>>> I did manage to solve this issue. >>>> >>>> It was one of the hardest issues I have had to >>>> deal with and I am not sure what exactly solved >>>> it. >>>> >>>> I did change the submission method to POST >>>> and had to chase through a lot of javascript to >>>> make sure all those ducks were in a row. >>>> >>>> I finally got it to work as expected. >>>> >>>> But not having any indication of why something >>>> is not working is the hardest, considering everything >>>> just before the apparent problem is working correctly. >>>> >>>> Thanks to any one who has considered >>>> this query to this point. >>>> >>>> JK >>>> > >> I actually found that browsers weren't the issue with long GET >requests but >> web servers were. In my particular case it was IIS, not sure if >Apache and nginx have the same issue. > >This is not an issue per se, more a sane limitation on client >misbehavior. >When webserver just accepted the connection and started parsing a >request, it >has to allocate some memory for initial buffer to read the request into >it. >Making this allocation bigger is not really feasible, and if your >request line >does not fit into it, it's safer to drop you and claim you are >misbehaving than >to keep reading in hopes of finding an end to your arrogance. I don't think I was arrogant, perhaps your choice of wording could be better? My point stands though, it's an issue as other web servers support longer GET requests without issue. It might be the reason why they say it's not fixable, but it is more likely that the problem there is the effort required yo fix against the benefits. Thanks, Ash
