some sites you visisted via this proxy may certainly caused 403 response.

[63514587]

1. Is bug reproducible with latest forwardproxy build?

yes

2. What are you trying to do?

help fix this bug,or show me how,thx.

3. What is your entire Caddyfile?

https://your_domain.xxx {
    basicauth / yourname yourpassword
    browse
    forwardproxy {
        basicauth absudra absudra!!!
        ports 443
        hide_ip
        hide_via
        acl {
        allow     *.caddyserver.com
        deny      192.168.1.1/32 192.168.0.0/16 *.prohibitedsite.com *.localhost
        allow     ::1/128 8.8.8.8 github.com *.github.io
#        allowfile /path/to/whitelist.txt
#        denyfile  /path/to/blacklist.txt
        allow     all
        deny      all # unreachable rule, remaining requests are matched by `allow all` above
        }
    }
}

4. How is your client configured?

via proxyomega as https proxy with successful connection.

5. How did you run Caddy? (give the full command and describe the execution environment). If multiple servers are used (for example with upstream), describe those as well.

/usr/local/bin/caddy -log stdout -agree=true -conf=/etc/caddy/Caddyfile -root=/var/tmp

6. Please paste any relevant HTTP request(s) here.

Usually,it works well.Sometimes ,such as visit blogspot,git.kali.org,etc.then it always return 403.googled that ,someone say ,which is caused by the website i visited had deplyed with $$,I dont know what means.

7. What did you expect to see?

wish to fix it.If it has difficult,then figure me how to avoid it.

8. What did you see instead (give full error messages and/or log)?

the chrome browser dev tools show nothing.
on the caddyserver side,i also couldnt find any clue.

9. How can someone who is starting from scratch reproduce the bug as minimally as possible?

I dont know.If you know,welcome your reply.

[63514587]

Im sorry,I have known the reason,which is caused by the feature of https proxy.sorry to disturb you.