Thanks. Sadly I know how the data is being pushed. It is poorly architected. Developers are working to re-write it but I am looking for a short term solution until they can complete that project. I found where windows is logging the error. I am just not sure which process writes to this log or how to tell it to ignore the error. I thought I had it with a registry entry but it didn't fix the problem.
C:\Windows\System32\LogFiles\HTTPERR 2023-03-09 23:55:40 192.168.103.30 56355 192.168.0.27 80 - GET - - 414 - URL_Length - On Thu, Mar 9, 2023 at 7:06 PM Terence M. Bandoian <tere...@tmbsw.com> wrote: > On 3/9/2023 5:47 PM, Jason Tan wrote: > > Hi Seth, > > One of my customer had the same error. We also tried increasing > maxHttpHeaderSize as suggested on Google. It worked for him for a while, > but he encountered the same error again later on. > > Our developers got involved and later discovered that our app was trying > to display all his favourites and the customer somehow managed to > accumulate a huge list of favourites. So, a hotfix was created to limit the > size of the favourites that get displayed on to the browser. > > I hope that helps you sort it out with the application to find what huge > data is being push onto the url and limit it. > > -----Original Message----- > > From: Mark Thomas <ma...@apache.org> > > Sent: Friday, March 10, 2023 9:34 AM > > To: users@tomcat.apache.org > > Subject: Re: HTTP Error 414. The request URL is too long. > > > > On 09/03/2023 20:59, Seth Mayers wrote: > >> I am running Apache Tomcat Version 9.0.48. > >> > >> If I post a transaction that is very large, I get the "414; The > >> request URL is too long". > >> > >> I have tried adding a bunch of parameters to my server.xml file but > >> none of them seem to work. I have tried: > >> maxHttpHeaderSize="262144" > >> maxSavePostSize="-1" > >> maxPostSize="-1" > >> maxHttpRequestHeaderSize="262144" > >> > >> I have someone that was able to resolve the same issue running Tomcat > >> 8.5 but his solution (maxhttpheadersize) did not work for me. Did > >> something change between 8.5 and 9.0.48 that might affect things? Is > >> something involved beyond just server.xml? > > Tomcat 9.0.x never returns a 414 status code. Wherever that status code > is originating, it isn't Tomcat. It must be in the application or in a > component before Tomcat. > > > > Mark > > > > > >> > >> SAMPLE POST (the one that fails is FAR larger than this) > >> > >> http://servername/gatewayAdminTest/GatewayClient?OutputType=1&InputTyp > >> e=1&Data=<request > >> name="CreateOrder"> > >> <Orders> > >> <Order> > >> <OrderHeader> > >> <WebTransactionType>LSF</WebTransactionType> > >> <CustomerID>010000092390</CustomerID> > >> <WarehouseId>02</WarehouseId> > >> <OrderSource /> > >> <PONumber>test_promo_freeProduct</PONumber> > >> <CarrierCode>DROP</CarrierCode> > >> <ReqShipDate /> > >> <ShipToNumber /> > >> <WebUserID>010000092391</WebUserID> > >> <WebOrderID>WEB001232</WebOrderID> > >> <OrderType>O</OrderType> > >> </OrderHeader> > >> <OrderDetail> > >> <LineItemInfo> > >> <ItemNumber>39012621</ItemNumber> > >> <OrderQty>1.00000</OrderQty> > >> <UnitOfMeasure>BAG</UnitOfMeasure> > >> </LineItemInfo> > >> </OrderDetail> > >> </Order> > >> </Orders> > >> </request> > >> &SubscriberID=xxx > >> -- > >> > > Are you sure that's POST request? I'd suggest looking at the Tomcat > access log if you can get a request that far. > > -Terence Bandoian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- [image: photograph] *Seth Mayers* Chief Technology Officer *p:* *e:* seth.may...@petfoodexperts.com www.petfoodexperts.com [image: facebook icon] <https://www.facebook.com/PFExperts> [image: instagram icon] <https://www.instagram.com/petfoodexperts> [image: linkedin icon] <https://www.linkedin.com/company/pet-food-experts> [image: twitter icon] <https://twitter.com/petfoodexperts> [image: youtube icon] <https://www.youtube.com/c/PetFoodExperts>
