reverse proxy response headers needed?

[justinrh 298]

Oh my, I'm getting a bunch of response headers from my Caddy RP that I'm guessing I don't need on the Internet.  Can someone confirm what is NOT needed for remote access?

access-control-allow-headers
Accept, Accept-Language, Authorization, Cache-Control, Content-Disposition, Content-Encoding, Content-Language, Content-Length, Content-MD5, Content-Range, Content-Type, Date, Host, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, Origin, OriginToken, Pragma, Range, Slug, Transfer-Encoding, Want-Digest

access-control-allow-methods
GET, POST, PUT, DELETE, PATCH, OPTIONS

access-control-allow-private-network
true

private-network-access-id

private-network-access-name

 

Man, it takes ~100 calls just to load the log in page 

Edited 28 minutes ago by justinrh

[js28194 76]

So confusing... non of this needed for a simple caddy reverse SSL reverse proxy.

At the most basic level you caddy file needs to look likes this 

{
    email myemail@gmail.com
}

emby.mydomain.com {
    log {
        output file C:\caddy\logs\emby_access.log {
            roll_size 5MiB # Set max size 5 MB
            roll_keep 2 # Keep at most 2 log files
            roll_keep_for 96h # Keep log files for 4 days
        }
    }

    reverse_proxy http://INTERNNAL_IP_ADDRESS:8096
}

You DON'T even need that entire Log block if you don't want it.

OBVIOUSLY your email is address is yours, and reverse proxy domain should reflect your domain and internal IP Address.

What you are trying to accomplish?