Not respecting URL path through Cloudflare tunnel

Aperta
#546 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
csharp, docker

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
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.

Image

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

Image
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

Lingua principale
C#
Stelle
2.4k
Fork
121
Merge medio
18g 20h
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di immichFrame/ImmichFrame

Tutte le issue di immichFrame/ImmichFrame

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.