Re^2: "Unexpected end of stream while looking for line"

I put 6000 because I suspected the timeout caused the 599 error. But that was not the case: the response should have come before 100 minutes.

Comment on Re^2: "Unexpected end of stream while looking for line"

Replies are listed 'Best First'.
Re^3: "Unexpected end of stream while looking for line" by 1nickt (Canon) on Jan 08, 2016 at 20:09 UTC
The remote server could have a front-end proxy with its own timeout limit exceeded by the process preparing the response. The way forward always starts with a minimal test.	[reply]
Re^3: "Unexpected end of stream while looking for line" by hotchiwawa (Scribe) on Jan 09, 2016 at 14:06 UTC
With 100 minutes, there is something wrong in the "flow" or "concept". You can't put a timeout of 100 minutes because the server should release the request and don't keep variables in memory or cache. The server performance will drop and you can have "server not responding", with the need to recycle or restart the server! Imagine you have 20 connections in 100 minutes, all will be kept during this time but there are other timeouts: session timeout, script timeout, execution timeout... and they are different, less...	[reply]