[FEATURE REQUEST] Custom header section to bypass different AUTH middleware

[AlexandruNegura]

**Is your feature request related to a problem? Please describe. **
Not sure if this is already available and I don't know about it.
My issue is that I do not use a VPN (yet) on my phone to access gotify.
I use Cloudflared where I setup that any request to my services must first be authenticated by CF Zero Trust.
I saw that CF Zero Trust allows you to set a specific CF TOKEN that will bypass that.
This would help others A LOT. Because ATM if I don't have a direct connection to my gotify instance remotely, the notifications cannot be decrypted and a random text message pops up in the iPhone.

Describe the solution you'd like
A section in the setup where you can set a custom header (the CF Client Token) which will bypass CF auth and make the Gotify Server available without a VPN.

Describe alternatives you've considered
The only solution I have is to create a wireguard server, set on my iPhone that all requests to local ips be redirected to the WG, and solve the issue. But this is not the case for all users and all setups.

Additional context
Thanks :D

[AlexandruNegura]

@androidseb25 Just wanted to know for starters if what I want is available already or not.

If not, it's ok. I get that this has no high priority since there are workarounds via VPN and stuff :D. And I am willing to wait for whenever this would be prioritised.

thanks

[androidseb25]

in the next Update you will find a new section in you're instance config -> Custom Headers

the progress for the new Update you will find here #143

[AlexandruNegura]

Thank you very much <3

[androidseb25]

Release 1.5 is imminent; app only needs approval from Apple.

[d7eeem]

@androidseb25

Apologies for reviving this issue.

I believe it would be more practical if the Custom Header configuration were available on the initial setup screen. This would allow authentication to occur before the request is sent through to the tunnel.

Currently, since the header can only be set later under Config > Custom Header, users have to either temporarily disable the Cloudflare authentication policy or connect using a local IP address before updating the configuration.

Integrating the header option earlier in the setup flow could streamline the process and avoid these workarounds.

[androidseb25]

@d7eeem thx for the hint i will bring it in the next iOS update