HTTP error-status results in net::ERR_INCOMPLETE_CHUNKED_ENCODING Cancel The title field is required!

1. Sascha Zehringer

   

   9 posts
   Registered:
   28 Oct 2022
   07 Oct

   Link to this post

   Hello Consultingwerk-Team,
   
   we got a problem, with throwing HTTP errors-status towards our Frontend. 
   A ERR_INCOMPLETE_CHUNKED_ENDCODING occurs with any HTTP-4xx status. And somehow it occurs on any chromium based browser, but not on Firefox or Postman and it does not happen while using plain cURL. E.g. throwing a HTTP-error 403 for no permission: this results in net::ERR_INCOMPLETE_CHUNKED_ENCODING 403 (Forbidden).
   
   This happens since, we updated our progress runtime from 12.2.13 to 12.2.16. 
   
   We are running SCL Release 11.7 #70894@2022-06-29.
   
   When I run %DLC_DIR%/servers/pasoe/bin/version.bat, this was the output:
   Server version: Apache Tomcat/9.0.30
   Server built:   Dec 7 2019 16:42:04 UTC
   Server number:  9.0.30.0
   JVM Version:    11.0.10+9
   JVM Vendor:     AdoptOpenJDK
   
   Unfortunately, I don't know which Spring version we are using.
   
   We suspect that the problem is either due to a misconfiguration of Spring or an incompatibility between all the versions. 
2. Mike Fechner

   

   342 posts
   Registered:
   14 Sep 2016
   07 Oct in reply to Sascha Zehringer

   Link to this post

   Just to clarify. The service is implemented using a @RestMethod or how?
   
   How is the 400 status returned? 
   
   It might be helpfui to log a support ticket at https://www.consultingwerk.com/support/issue-tracking and also attach a HAR file with the request details.
   
   If this only happens in Chrome and not in Firefox, it might be helpful to attach a HAR file of the request in both browsers: https://support.zendesk.com/hc/de/articles/4408828867098-Generieren-einer-HAR-Datei-zur-Fehlerbehebung#h_01HRYRY6VQVR5K6SRVAVNQ4XT0
3. Sascha Zehringer

   

   9 posts
   Registered:
   28 Oct 2022
   07 Oct

   Link to this post

   I'm sorry, I forgot to mention the main problem.
   The Response Body of the HTTP-4xx Status is always empty on chromium based browsers.
   The problem occurs with @RestMethod and @RestAddress. 
   
   I created a more detailed jira-ticket, since i don't want to show the URLs and stuff.
4. Sascha Zehringer

   

   9 posts
   Registered:
   28 Oct 2022
   07 Oct in reply to Sascha Zehringer

   Link to this post

   The Ticket is SCLSUP-623.