Not respecting URL path through Cloudflare tunnel
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp, docker
- Domain
- frontend, infrastructure
Research direction
The payload names no source files, only a Docker deployment behind a Cloudflare tunnel with a URL path prefix, and asset requests going to /_app/ instead of /full_path/_app/. Start by reproducing with a reverse proxy that strips or adds a path prefix, then find where the app builds its asset and content URLs. Done means the generated URLs keep the client's path prefix. The Configuration section is empty, so the config and log files need to be gathered first.
Written by the indexing model from the issue text.
Description
Version
v1.0.48.0
Deployment Method
Android
Description
I'm trying to deploy ImmichFrame on several Android tablets for family.
I'm running separate Immich-Frame docker instances on separate ports with separate AuthenticationSecrets to control which Albums each Immich-Frame instance can display.
The goal is to use CloudFlare Tunnel Connectors to provide external access to the different instances by URL Path.
As seen in the screenshot below, the initial request comes in properly with the full path and auth secret (bottom line). Then the next request comes in for chunks at /_app/ instead of /full_path/_app/. It is getting a 404 response from Cloudflare at this point.
I know I could break these requests up to different hosts, but I would rather use URL paths instead of hosts. It seems like the content URL's being generated by immichFrame are not respecting the full path of the client request when generating the content URL's.
Reproduction
Cloudflare Connector with basic settings
Expectations
No response
Configuration
Logs
Pre-Submission Checklist
-
This is a bug report and not a feature request
-
I have provided all of the required information to reproduce the bug (config, logs, etc.)
-
I have checked for related issues and checked the documentation
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 121
- Avg merge
- 18d 20h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from immichFrame/ImmichFrame
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
immichFrame/ImmichFrame#735 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
immichFrame/ImmichFrame#733 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
immichFrame/ImmichFrame#732 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 22/100
immichFrame/ImmichFrame#731 · 1 reaction ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
immichFrame/ImmichFrame#729 ·
All issues in immichFrame/ImmichFrame
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
dotnet/EntityFramework.Docs#5521 ·
Maintainers usually reply within 1 day
-
Feature needs response
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Adyen/adyen-dotnet-api-library#1907 ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dimitar-radenkov/Pointframe#318 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DotHarness/dotcraft#546 ·
Maintainers usually reply within 1 day
-
a-corriger bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
christian-raj/S-Aloha#303 · 1 comment ·