Possible addition to migration guide

[krishna-devolo]

This is in relation to a previously closed issue: https://github.com/eclipse/hawkbit/issues/957. For those of us who use hawkBit with a SSL reverse proxy, the migration guide for M7 could potentially point to an important change: Use server.forward-headers-strategy=NATIVE instead of the now deprecated server.use-forward-headers=true. This information is available in Spring Boot 2.2 Release Notes, but, in my opinion, would be a welcome addition to the migration guide. (We took over a month in our firm to figure this out. 😢)

[bogdan-bondar]

Big thanks for pointing this out! Will be fixed with https://github.com/eclipse/hawkbit/pull/1225

[martinetd]

Hello @krishna-devolo (and others),

I'm pretty sure I had gotten this working back in october, but I can't get the artifact download links to work again when proxied without explicitly setting hawkbit.artifact.url.protocols.download-http.protocol/hostname and ref...

If you or someone else have a working example somewhere I'd really appreciate it.

FWIW my proxy is setting the following headers:

X-Forwarded-For: <client_ip>
X-Forwarded-Proto: https
X-Forwarded-Host: <public_host>
X-Forwarded-Port: 443
X-Real-IP: <client_ip>

and I've also had problems with spring not reading my application.properties (some default mysql settings embedded in the jar file seem to win over /opt/hawkbit/application.properties?) so tried setting server.forward-headers-strategy=NATIVE via env var to no avail... It's sending clients to fetch with plain http toward the internal port, but with the host ip from X-Forwarded-Host so I don't get what it's trying to do.

For now I have the workaround of setting the ref explicitly but this is something we need users to setup so having this kind of settings picked up automatically would really be better... And for some reason I'm convinced I had gotten it working at some point.