I create a uniq connection ID on my child proxy (for later logging). I send this ID to my parent via http-header. On the parent I receive the ID by using Header.Request.Get. This value is written to a user defined variable. I like to log the uniq ID on the child proxy AND the parent proxy. This helps to aggregate logs later on.
This works fine for http and https without ssl scanning. As soon as I use ssl scanning the header value within Header.Request.Get is not accessible any more. It's available for the initial CONNECT. But not for all the https elements within the SSL-Scanning. So I am not able to log the uniq ID for all the SSL scanned objects. Even if I write the value of Header.Request.Get to a user define variable the variable is empty as soon as Web Gateway processes the elements within the SSL scanning.
I seem within ssl scanning all the defined variables are gone. Any ideas why? Maybe ssl scanning is a whole new cycle, even if it's the same https-connection. But even then I should be able to read the header from Header.Request.Get again. But this also does not work. Value is empty.
Any ideas? I think it's a bug. But maybe I am wrong or there is another way to do this.
https CONNECT. All good. Same for http:
Problem with https within SSL scanning
Solved! Go to Solution.