Gate shares behind magic-link sessions, add comments and new-photo email digests

This commit is contained in:
zyphlar
2026-10-19 15:10:57 -07:00
parent c8d8dc9dbc
commit f598200e24
34 changed files with 3387 additions and 375 deletions
+10 -6
View File
@@ -138,7 +138,9 @@ With it off, a slug link gets a 404 and only the key form works.
## `uploadUrl`
**Type:** `string` · **Default:** `"/upload"`
**Type:** `string` · **Default:** `""`
Off by default in this fork: the upload service does not check magic-link sessions, so anyone with a share key could reach its upload page.
Where the optional upload service (the `immich-public-proxy-upload` container) is served. A share whose "Allow public user to upload" option is on in Immich then shows an "Add photos" button in the gallery header, which opens that share's page on the upload service. To set up the service, see [Let visitors send photos back](/visitor-uploads).
@@ -184,16 +186,18 @@ Send a custom response instead of the default 404. See [Error responses](/config
**Type:** `object`
Change the headers sent with photos, videos and static files. The default is a 30-day `Cache-Control` and a
permissive CORS header. The "download all" zip is always sent with `Cache-Control: no-store`, and the gallery page
uses its own [`gallery.cacheTime`](/config/gallery#cachetime).
Change the headers sent with photos, videos and static files. The default is a 30-day browser-only `Cache-Control`.
The "download all" zip is always sent with `Cache-Control: no-store`, and the gallery page with
`Cache-Control: private, no-cache`.
In this fork every photo sits behind a magic-link session, so keep `Cache-Control` `private`: a `public` value lets a
CDN or shared proxy store a photo and hand it to anyone who asks for the same URL.
```json
{
"ipp": {
"responseHeaders": {
"Cache-Control": "public, max-age=2592000",
"Access-Control-Allow-Origin": "*"
"Cache-Control": "private, max-age=2592000"
}
}
}