mlibbey

Think you'd need the CONNECT to be initiated by the client like curl -p -v -x 127.0.0.1:8080 https://download.docker.com/linux/ubuntu/ (and I think you'd do the mapping like map https://download.docker.com https://download.docker.com:443 )

Think your next debugging step would be to get on the node running ATS, and find a (verbose) curl that works -- that should help in figuring out how to...

FWIW, we have proxy.config.url_remap.remap_required: 1 but, our mapping rules have the origin's port -- like map https://example.com https://example.com:443 without the port, the requests fail.

Interesting -- we only have the port on the origin side of the mapping. Also, FYI, took me forever to get CONNECT over https working -- the curl incarnation was...

I did test that in our environment -- not having the port on the origin side of the mapping leads to a 403 Tunnel Forbidden on the "inner" connection"; while...

mhomaid1 -- could you test with and without port on the inbound side of the mapping? The community always welcomes pull requests especially for documentation improvements!

@JakeChampion because of big recent changes to compress.

Sorry for the initial build failures -- it was building locally :( (The Rocky crash looks to be in a cache subsystem regression test). Think it really ready for review.

If I'm understanding correctly you can set [proxy.config.srv_enabled](https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.yaml.en.html#proxy-config-srv-enabled) to 1 to use SRV for the origin -- so if you had map http://mywebsite.tld https://origindomain.tld with the setting (either in records.yaml...

I'd love to improve the docs! What about adding more to the example. Like, ``` For instance, if the origin is set to https://my.example.com, Traffic Server would lookup the SRV...