AFAIK: A http POST request is sent to apache, then piped through stdin and into a CGI program.
Does apache guarantee that the stdin stream will always have an EOF ?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
AFAIK: A http POST request is sent to apache, then piped through stdin and into a CGI program.
Does apache guarantee that the stdin stream will always have an EOF ?
EOF isn’t a “character” or “marker” in the input; EOF is an error when attempting to read and not having more data available. Calls such as read or fread will return this as an error, such as reporting less was read than was requested. (There is an EOF macro in C, but it’s treated as an error code and isn’t an actual character.)
EOF is signaled by the OS, not Apache, and even though Apache could pull some dirty tricks (such as keeping the stream open but never writing), it doesn’t.