Interface timeout 502badgateway timeout limit when the page fails to call the interface, the response is 10 s. Through xhprof monitoring, it is found that the interface call times out. But in fact, when the interface times out, it can only be 2 s at most, and the read stream time-out is limited through stream_set_timeout. Query manual... interface timeout 502 bad gate way timeout limit invalid
When the page calls an interface, the response is 10 s. Through xhprof monitoring, it is found that the interface call times out. But in fact, when the interface times out, it can only be 2 s at most.stream_set_timeout
The read stream timeout limit is imposed.
Query manual
There are some examples in the manual, some of which are described as follows:
If you are using fsockopen() to create a connection, first going to write into the stream and then waiting for the reply (e.g. simulating HTTP request with some extra headers), then stream_set_timeout() must be set only after the write - if it is before write, it has no effect on the read timeout :-(
But in fact, logical modification according to this writing method is still invalid.
How can I solve this problem?
Reply content: interface timeout 502 bad gate way timeout limit invalid
When the page calls an interface, the response is 10 s. Through xhprof monitoring, it is found that the interface call times out. But in fact, when the interface times out, it can only be 2 s at most.stream_set_timeout
The read stream timeout limit is imposed.
Query manual
There are some examples in the manual, some of which are described as follows:
If you are using fsockopen() to create a connection, first going to write into the stream and then waiting for the reply (e.g. simulating HTTP request with some extra headers), then stream_set_timeout() must be set only after the write - if it is before write, it has no effect on the read timeout :-(
But in fact, logical modification according to this writing method is still invalid.
How can I solve this problem?