Unable to follow 307 redirections

[djrarky]

I'm ussing immich upload optimizer to losslessly compress images, but when using immich-go, it refuses to allow 307 redirects. A single photo uploads upon every run, but then fails.
https://github.com/miguelangel-nubla/immich-upload-optimizer

It has been identified to be an issue with immich-go, is it possible to allow the app to follow 307 redirects? Thank you so so much!

miguelangel-nubla/immich-upload-optimizer#15

[simulot]

It more complex than expected.

[simulot]

Considering this idea:

Immich-go detects duplicates based on the file name and file size. Immich detects duplicates based on the file's hash.

I believe the optimization process will undermine all deduplication efforts because both the file size and hash are affected by optimization.

The first time a file is uploaded, Immich stores an optimized version of the image.

The next time, Immich-go will not recognize the file due to the size difference and will submit it to Immich, where it undergoes optimization again. If the optimization results in the same file, Immich will reject it, making the optimization and the upload redundant. If the optimization generates a slightly different file, Immich will accept it, leading to duplicate images.

[ArnaudCrl]

I just stumbled upon this exact issue when immich upload optimizer and immich-go try to interact. It would be nice to have a fix or a workaround. Thank you for your work !

[kotx]

Maybe we could feature request immich-upload-optimizer to return a X-Optimized-File-Hash header or something.

[simulot]

I don't think it is needed. The 307 is detected but it's difficult to handle directly. The 1st 32k of the flow are consumed during the initial call, and must be resubmitted to the redirected address.

I need to change the way of building the upload flow to cope with this. It's on my todo list, after the stabilization