Update CachedRequestService.php

[erdogan-work]

• Resolves: 504 Gateway Time-out when enabling richdocuments #1486
• Target version: main

Otherwise I get a timeout instead on this page:

[elzody]

This might be one for @juliusknorr to review since I am unsure about the implications of this and he worked on it.

[juliusknorr]

Can you share more details about your setup? Are you using the built-in CODE server (richdocumentscode app) or a dedicated collabora server as docker or package installation? The timeout is probably way too large for usual setups where i would expect the requets to finish faster then 1 second

[erdogan-work]

Sure!
It's a Nextcloud 30.0.5 Enterprise, built-in Collabora Online Development Edition 24.04.11.2 b6712dc6c4.
It's visible in the screenshot I uploaded.

Its a Linux SLES 15 SP 6.
Directly installed as OS Packages without docker.
We use php8-fpm with apache2 Webserver.

I got timeouts when tried to open office documents and read in the logfiles about the expired timout.

Umut Erdogan

[juliusknorr]

Can you do a manual curl request towards https://yourcollaboraurl/hosting/discovery on the Nextcloud server and measure the time? We should really avoid such long timeouts and I'd rather expect some setup issue there then.

[erdogan-work]

The Url with https://yourcollaboraurl/hosting/discovery displays an error page:

It took this time:
real 0m0.081s
user 0m0.020s
sys 0m0.008s

The Url https://yourcollaboraurl/apps/richdocumentscode/proxy.php?req=/hosting/discovery
shows the expected xml file:

It took this time:
real 0m0.028s
user 0m0.019s
sys 0m0.004s

Maybe I can try it with the original settings for a while to test whether it would now work?

KR
Umut Erdogan