HTTPS Inspection Bypass

[CaseyB]

Running into an issue where I need to bypass HTTPS inspection (R81.10 JHF 150); however, this is the URL:

https://eka-prod-xxx.s3-eu-west-1.amazonaws.com - xxx is the wildcard. Is there a good way to handle this?

The full URL in this case ended up being:

eka-prod-survey-binaries-active-bucket-e1lw1wtq8m9jg38i.s3.eu-west-1.amazonaws.com

[the_rock]

I just tested in the lab and worked fine, added to bypass rule like below.

Andy

 

[CaseyB]

https://eka-prod-xxx.s3-eu-west-1.amazonaws.com/ isn't the actual URL it is using though, XXX is a placeholder for numerous other names.

I could add the highlighted URL to resolve the issue, but that section is dynamic and will be something else later. That's why I need to be able to do some sort of wildcard for the XXX portion of https://eka-prod-xxx.s3-eu-west-1.amazonaws.com/.

[the_rock · Accepted solution]

Easy peasy...just add *eka-prod* as wild card, thats what I did, no issues.

Andy

[CaseyB]

Ah, perfect, thanks! I forgot about the * wildcard option within custom Application/Site.

[the_rock]

All good...we are here to help 🙂

Andy