You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running Nextcloud 27.0.1 and CollaboraOnline CODE 23.05.2.2 (installed from your deb-packages repository) on the same server.
My server OS is Linux Mint 20.1.
Nextcloud uses app 'richdocuments' to produce preview of PDF and Office docs. App Richdocuments uses Guzzle to send (via apache reverse proxy) the request:
POST /cool/convert-to/png HTTP/1.1 / Host: the.name.of.my.host.net / Expect: 100-Continue / Content-Type: multipart/form-data; boundary=aae3d303568bfddc5e50234056e4475d5bc1ab77 / User-Agent: Nextcloud Server Crawler / Accept-Encoding: gzip / X-Forwarded-For: 192.168.0.1 / X-Forwarded-Host: office.invara-erde.freeddns.org / X-Forwarded-Server: the.name.of.my.host.net / Content-Length: 2572543 / Connection: Keep-Alive
Note the 'Expect: 100-Continue'. This is present when the document to be converted is large.
Apparently conforming the HTTP standard, Guzzle waits for a '100 Continue' reply from the CODE server before sending the contents of the document to be converted.
However, the CODE server does not always send a '100 Continue' reply. This causes the apache process running Guzzle to hang, and no preview is sent to the browser.
Furthermore, this issue also causes large nextcloud PDF files not to be displayed properly in the browser.
In my humble opinion, the problem might be located in method StreamSocket::parseHeader() around line 1160.
My understanding of the code is that only the first time a 'Expect: 100-Continue' is encountered, CODE will send '100 Continue'. However, I wonder why not every 'Expect: 100-Continue' gets its '100 Continue' reply. My understanding of the HTTP standard is that this should be sent each time, unless the request is already complete (which isn't the case here because the document contents is still to follow).
The text was updated successfully, but these errors were encountered:
I am running Nextcloud 27.0.1 and CollaboraOnline CODE 23.05.2.2 (installed from your deb-packages repository) on the same server.
My server OS is Linux Mint 20.1.
Nextcloud uses app 'richdocuments' to produce preview of PDF and Office docs. App Richdocuments uses Guzzle to send (via apache reverse proxy) the request:
POST /cool/convert-to/png HTTP/1.1 / Host: the.name.of.my.host.net / Expect: 100-Continue / Content-Type: multipart/form-data; boundary=aae3d303568bfddc5e50234056e4475d5bc1ab77 / User-Agent: Nextcloud Server Crawler / Accept-Encoding: gzip / X-Forwarded-For: 192.168.0.1 / X-Forwarded-Host: office.invara-erde.freeddns.org / X-Forwarded-Server: the.name.of.my.host.net / Content-Length: 2572543 / Connection: Keep-Alive
Note the 'Expect: 100-Continue'. This is present when the document to be converted is large.
Apparently conforming the HTTP standard, Guzzle waits for a '100 Continue' reply from the CODE server before sending the contents of the document to be converted.
However, the CODE server does not always send a '100 Continue' reply. This causes the apache process running Guzzle to hang, and no preview is sent to the browser.
Furthermore, this issue also causes large nextcloud PDF files not to be displayed properly in the browser.
In my humble opinion, the problem might be located in method StreamSocket::parseHeader() around line 1160.
My understanding of the code is that only the first time a 'Expect: 100-Continue' is encountered, CODE will send '100 Continue'. However, I wonder why not every 'Expect: 100-Continue' gets its '100 Continue' reply. My understanding of the HTTP standard is that this should be sent each time, unless the request is already complete (which isn't the case here because the document contents is still to follow).
The text was updated successfully, but these errors were encountered: