[codex] limit FHEM upstream concurrency#99
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b4b586880
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: de5bb8031d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 631eeace0d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| try_files {path} /__fhem_backend/fhem{uri} | ||
| handle_path /__fhem_backend/* { | ||
| reverse_proxy https://fhem-fhem-1.network_backend_net:8088 { | ||
| transport http { |
There was a problem hiding this comment.
Apply the FHEM connection cap to image fallback
When an image is absent from /srv/fhem-www (or the new bind mount is unreadable), this newly added fallback still proxies the /fhem/images/* burst to fhem-fhem-1:8088 through its own inline transport http. Caddy documents max_conns_per_host as a transport http option that limits that transport's connections, but this transport neither imports fhem_transport nor sets the cap, so the exact fallback path for missing/custom images bypasses the 20-connection mitigation.
Useful? React with 👍 / 👎.
What changed
max_conns_per_host 20in the sharedfhem_transportblock.Why
401responses from FHEM and occasional502dial timeouts from Caddy.Validation
curlrequests.Notes