does phpClientHttpsFix or the OVERWRITEPROTOCOL env variable actually do anything?
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
I see a lot of issues trying to fix CSP issues by using the phpClientHttpsFix.enabled = true variable (which sets up the OVERWRITEPROTOCOL env variable on the pod)
However, a quick search of the actual nextcloud repo shows that this environment variable is referenced nowhere. Personal testing with this variable led to nothing happening at all...
On the converse, it appears that it's necessary to set the 'overwriteprotocol' => 'https' config variable if you want the desired behavior.
<?php
$CONFIG = array (
'overwriteprotocol' => 'https'
);
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how phpClientHttpsFix.enabled produces OVERWRITEPROTOCOL in the Helm chart, then compare that behavior with the referenced Nextcloud repository search and the overwriteprotocol configuration example. Done means establishing whether the chart setting is consumed and identifying the configuration path that provides the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, php
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100