Incorrect QR code generated (missing absolute URL)

[christianstrauch]

Hi all,
since today's update of the Docker image to HB 0.23, I am experiencing an issue with the generation of QR code labels:
The QR codes on item labels do not include the scheme and host name any more - they just include the relative path to the item (i.e., /a/000-000 instead of https://example.com/a/000-000).
The logs show the follow error:
ERR ../go/src/app/app/api/handlers/v1/helpers.go:23 > failed to parse URL error="parse \":7745\": missing protocol scheme"

This installation is behind a reverse proxy, internal web port inside the container is 7745, the container does not expose any ports, NGINX acts as a reverse proxy on the same docker network. X-Forwarded-... headers are properly configured, as is web socket proxying - I have not changed any configuration since today's update from 0.22.3 to 0.23; QR code generation has worked just fine before.

Is anyone else experiencing this issue?

Thanks

[BuenyaminSarikaya]

Same issue here with Nginx reverse proxy.
Workaround: The label generator at /reports/label-generator works correctly – Base URL is properly detected and QR codes contain the full absolute URL.
Bug: The "Print Label" button on individual item pages generates QR codes with only the relative path (/a/000-001) instead of the full URL.
Edit: Generate Page button does not work for me, but Web browsers "Print Page" on /reports/label-generator works just fine.

[chrisp250]

There seems to be another issue with QR codes #1283
I added the detail of this bug under this issue.
I also tried the Demo and QR code generation and there it works fine.

[tankerkiller125]

I've pushed a fix to main that will hopefully resolve this issue. The previous QR code generator was using the Referer header exclusively to determine the URL to set with a very basic (and not great) fallback. It will now use the Hostname configuration option, or if you have the trust proxy option enabled it will also attempt to use the proxy headers.

This issue was caused by a change to the security headers that Homebox sends, resulting in some browsers not sending a Referer header.