trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lei Sun <lei....@gmail.com>
Subject Re: [E] https issue
Date Sat, 05 Dec 2020 19:04:53 GMT
Hi Guys,

I was able to figure out how to do this with Squid's cache_peer feature.

> cache_peer 23.105.0.211 parent 29842 0 no-query no-digest
> login=USERNAME:PASSWORD
> never_direct allow all


Squid was able to essentially forward my request to *23.105.0.211*, plus
the basic auth, and return the result

> $ curl --proxy http://127.0.0.1:3128 https://httpbin.org/get?answer=42
> {
>   "args": {
>     "answer": "42"
>   },
>   "headers": {
>     "Accept": "*/*",
>     "Host": "httpbin.org",
>     "User-Agent": "curl/7.54.0",
>     "X-Amzn-Trace-Id": "Root=1-5fcbd8a7-5a21842b590a9e1637bdc520"
>   },
>   "origin": "*23.105.0.211*",
>   "url": "https://httpbin.org/get?answer=42"
> }


Question:
1) How can I make ATS do the same thing?
2) Can I use a lua script to do this? (I was able to do this with a normal
forward proxy configuration plus a lua script to rewrite headers & next
host address for normal http successfully, but failing for https requests
somehow. What should be done so that this could work, please?)

Thank you!
Lei

Mime
View raw message