cURL time out

[jlssmt]

• Resolves: --

Summary

Fixed cURL regarding:
https://help.nextcloud.com/t/curl-error-28-operation-timed-out-after-30000-milliseconds-with-0-bytes-received-federated-nextcloud/113088

TODO

--

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[kesselb]

Reason for 30 seconds: #16972

Afaik, we overwrite the default timeout if necessary, but default should stay 30.

[PVince81]

would it make sense to make the timeout configurable, specifically for federated shares ?

[come-nc]

Increasing timeout here does not feel like a good solution.
If the problem only arise for big files there may be a problem with how the connection is handled. It should start recieving data fast even if the file is big.

[nicoduck]

Since this currently affects me with downloading a big file from a federated share, I'd like to see that as a configuration option.

[kesselb]

Fixed by #38292

[kesselb]

OCA\Files_Sharing\External\Storage extends OC\Files\Storage\DAV.

Therefore, the value of davstorage.request_timeout apply.

There are additional HTTP requests in OCA\Files_Sharing\External\Storage.getShareInfo and OCA\Files_Sharing\External\Storage.getShareInfo.testRemoteUrl not using the parent class timeouts. If someone runs into timeouts, feel free to send another pull request and adjust private $timeout to protected $timeout and use them in the child class.