> ...From the client's POV - verified with strace
> - the POST request went out at 11:16:10, and the response was received
> at 11:16:21.
...
> 21827 11:16:10.042475 connect(12, {sa_family=AF_FILE, path="/var/run/
apache2/wsgi.11746.39.2.sock"}, 110) = 0
...
> 21827 11:16:10.124810 shutdown(12, 1 /* send */) = 0
> 21827 11:16:10.124930 read(12, <unfinished ...>
> 21827 11:16:21.917191 <... read resumed> "Status: 200 OK\r\nVary:
> Cookie, Us"..., 8000) = 2125
>
> Due to the successful shutdown(), I would expect the client to receive
> the response at that time, but as mentioned, it doesn't receive it
> until the follow-on read unblocks.
The shutdown() is called with SHUT_WR (1), which means that
there is a socket half-close situation. This prevents additional
data from being sent by Apache to the wsgi process. However
it has no effect on the reading of data in the other direction.
Generally the shutdown acts like an end-of-file marker,
it shouldn't affect the delivery of packets or their timing.
A pattern of using half-closes is not unusual and shouldn't
cause any unexplained delays; though it may require somebody
with more modwsgi internals knowledge to answer definitively.
Aside from the unexplained 11 second delay, are your requests
otherwise working okay; or are they failing in some manner?
--
Deron Meranda
http://deron.meranda.us/
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
