Changes between Version 8 and Version 9 of help/en/howto/mount/issues/fastcgi

Timestamp:

Jan 24, 2018 1:46:59 PM (19 months ago)

Author:

dkocher

Comment:

--

help/en/howto/mount/issues/fastcgi

@@ -19 +19 @@
 In step 3 [https://mountainduck.io Mountain Duck] opens a connection to the remote server, sends a `PUT` request with the http header `Transfer-Encoding: chunked` and streams through all subsequent write callbacks. Finally in step 6 the connection is closed.
 
-Since the expected length is missing in the header the streaming characteristic of such requests makes them more difficult to be handled in the components being passed. From our research the issue only exists in environments that use FastCGI to speak to their PHP application. Related bug reports - [https://bugs.php.net/bug.php?id=60826 here] and [https://bz.apache.org/bugzilla/show_bug.cgi?id=53332 here].
+Since the expected length is missing in the header the streaming characteristic of such requests makes them more difficult to be handled in the components being passed. From our research the issue only exists in environments that use FastCGI to speak to their PHP application. See related bug reports
+ * [https://bugs.php.net/bug.php?id=60826 PHP Bug #60826 Raw POST data missing with chunked encoding, FastCGI] 
+ * [https://bz.apache.org/bugzilla/show_bug.cgi?id=53332 Apache HTTPD Bug 53332 - Requests with chunked encoding have no body available to FCGI backend].
 
 The nginx developers try to work around this issue by simply buffering the entire incoming stream and forward it through the FastCGI interface as a request with a well-known length. Nginx does request buffering by [http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_request_buffering default]. There are several [http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html options] to adjust the buffering behaviour.