This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 72%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
I am no able to post a question. After successfully went trough captcha, I see an error:
My topic was about IIS:
....
IIS php fast-cgi and chunked request body
I've found out IIS doesn't support a chunked request bodies, eg.
I found a mention:
In HTTP/1.1, chunked transfer encoding is primarily a server-side response mechanism. The specification (RFC 9112, previously RFC 7230 and RFC 2616) defines chunked encoding as a way for the server to send responses when the content length is unknown in advance.
However, HTTP/1.1 does allow chunked requests, but support for them is optional for servers. Many web servers, including IIS, do not support chunked request bodies, meaning they do not accept incoming requests that use chunked transfer encoding.
Anyway. In my scenario the curl never returns and still blocks a IIS/php-cgi.exe process. On a second request it starts second php fastcgi php-cgi.exe process untill a maximum configured (eg. 16).
In that case everything is blocked and no other clients like browser are served by php-cgi.
Still I can get a static content but the php application is stucked.
Why IIS doesn't respond something like HTTP 400 Bad Request etc. ?
Can I still configure IIS to accept chunked request bodies?
It is very funny, also my post to this was blocked because of curl cmdline snippet
Finally, the curl as an image helped ...
https://learn.microsoft.com/en-us/answers/questions/2236351/iis-php-fastcgi-and-chunked-request-body
But as markdown not.
Hi,
I tested the same content using Markdown and didn’t encounter any issues. Usually, logging out and back in/clearing browser cache resolves this problem.