> On Apr 1, 2019, at 2:39 AM, Alexander Rabenstein
> <[email protected]> wrote:
>
> Hi,
>
> I am trying to figure out if its technical possible with Traffic Server to
> achieve the following:
>
> Client requests http://domainx.internal <http://domainx.internal/>/index.html
> using trafficserver in forward proxy mode.
> Trafficserver serves the requested page, the pages contains <img > links to
> https://domainy.internal/xyz <https://domainy.internal/xyz>
> Clients requests https://domainy.internal/xyz <https://domainy.internal/xyz>
> Trafficserver remaps to http://domainz.internal/ <http://domainz.internal/>
> and aborts the ssl tunnel from the client..
>
> I got the configuration so far working as the remaping of the hostname is
> done, but the client first sends a CONNECT request, and ts is forwind this to
> the origin server on port 80, which the origin can’t handle
Pretty sure what you are asking to do is not possible, at least I can’t think
of a way. If your client is setup to do forward proxy for HTTPS, then it will
do CONNECT. To avoid the mapping to port80, you would just need to have either
an open proxy (not recommended) or a rule like
map https://domainx.internal <https://domainx.internal/>
https://domainx.internal <https://domainx.internal/>
Alternatively, if you truly want to change from HTTPS -> HTTP, you would need
to rewrite the HTML returned for the index.html page. This can be done with a
transform plugin, but I don’t think we have one that does exactly this.
— Leif
>
> Gruß,
>
> Alex
>
> Alexander Rabenstein – Application Management Retail - Tel: 455 077
