Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to make Apache accept requests, without waiting for client to recv responses?
    primarykey
    data
    text
    <p>I wrote a simple socket send routine that sends multiple HTTP requests to apache, essentially logging some data into database (WinSock TCP/IP->Apache->PHP->MySQL). I send HTTP POST request, wait for 200 OK response, then send another HTTP POST request, wait for 200 OK response, ... many times over the same socket. The request-response roundtrip takes ~100 ms. I can't send the next request until I read the response to the previous request, Apache just won't process the requests like that. Otherwise it works fine (if slow).</p> <p>I'd like to be able to send a continuous stream of requests to Apache, regardless of the responses. I'm ok if the socket closes and some requests will be dropped mid-stream, but if all requests generate "200 OK", I'd like to just send a bunch of packets to Apache, and let Apache process them one by one, responding to each in order. Or even not responding, I don't really care in this particular case.</p> <p>Is there any way to configure Apache to do that? I don't know enough about sockets to understand why it's necessary to wait to receive HTTP response before sending the next request. I don't know of any fundamental problem with just queuing requests on Apache side, and responding to them in order without waiting for ACK from the client. It probably breaks some protocol rules to queue multiple HTTP requests if they're sent as one packet, but I'm hoping Apache has some way to process this situation. Any help or explanation as to why this is impossible would be appreciated. </p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload