trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Wederbrand <>
Subject Re: [E] pssc/proxy response status code: 000
Date Tue, 08 Dec 2020 17:50:05 GMT
Yeah, that was my thought as well, but it isn't the origin. The api is
test-api that sleeps for 35 seconds and with some clients (like curl or
insomnia) this always works, with other it never works (I guess it's apache
http client at the bottom of these).

So I've tried to reproduce it with a timeout setting in curl, I still don't
get 000, I get 200 according to the ats-logs, even if the client was gone
long before.

Also, if the origin times out based on settings in ats I think it returns
504 to the client.

On Tue, Dec 8, 2020 at 5:18 PM Susan Hinrichs <>

> It means that ATS did not get an origin response before the transaction
> ended.  If the transaction lasted 30 seconds, it seems likely that your
> client or origin timed out.  Either due to the inactivity_timeout's set in
> ATS, or due to timeout logic in the client or origin.
> On Tue, Dec 8, 2020 at 8:55 AM Andreas Wederbrand <>
> wrote:
>> Hi!
>> I'm running ATS (7.x) as a reverse proxy and I'm seeing something weird.
>> For some clients I get pssc = 000 on the exit, for most it's 200.
>> This always happens after 30 seconds but ats i configured to allow longer
>> requests than that, and with curl or insomnia it happily runs for 30+
>> seconds.
>> I've tried to set at timeout both in curl and insomnia to check if 000
>> means that the client went away but ats happily logs the result with
>> duration or 30+ seconds, long after the client terminitade.
>> So, I guess the question is: what does pssc = 000 mean?
>> Thanks.

View raw message