Open shadeofblue opened 1 year ago
while working on the GasTracker app, it was found out that sometimes, the returned API responses were incomplete...
the route was:
browser -> nginx on the front-end -> back-end
the content was okay when the browser accessed the back-end directly
the suggestion is that the particulars of the nginx configuration on the front-end node (chunked encoding?) caused some trouble
@shadeofblue please provide a context for what it means the response were incomplete - whether it had it's content stripped, invalid response returned, request failed with status code 4xx or 5xx or we just saw the page is not responding
@VanDavv unfortunately, I'm unsure now what the exact status was -> I believe the browser was just waiting for the full response indefinitely but don't remember now
While working on the GasTracker app, it was found out that sometimes, the returned API responses were incomplete.
The route was:
browser -> nginx on the front-end -> back-end
The content was okay when the browser accessed the back-end directly.
The suggestion is that the particulars of the nginx configuration on the front-end node (chunked encoding?) caused some trouble.
Todo: