TCP::Respond as part of HTTP CONNECT request/response

Hi guys,

boneyard, yes i'm sending both http/https to the same port.

I created a very simple irule just for testing with the following statements.

set html_message "Access DeniedAccess Denied"

TCP::respond "HTTP/1.1 403 Not Allowed Mime-Type: text/html\r\nCache-Control: no-cache,no-store\r\nConnection: close\r\nContent-Length: [string length $html_message]\r\n\r\n$html_message\r\n\r\n"

I'm running wireshark on my client and the responses look the same. Both show "269 HTTP/1.1 403 Not Allowed Mime-Type: text/html" in the summary. And if I look look deeper the HTTP portion looks identical as well.

If I attempt to access http://google.com I get the access denied message. Here is what wireshark displays if I follow the TCP stream.

GET http://google.com/ HTTP/1.1
Host: google.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-GB,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive

HTTP/1.1 403 Not Allowed Mime-Type: text/html
Cache-Control: no-cache,no-store
Connection: close
Content-Length: 89

Access DeniedAccess Denied

If I attempt to access https://devcentral.f5.com I get the proxy server is refusing connections message. Here is what wireshark displays if I follow the TCP stream.

CONNECT devcentral.f5.com:443 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: devcentral.f5.com:443

HTTP/1.1 403 Not Allowed Mime-Type: text/html
Cache-Control: no-cache,no-store
Connection: close
Content-Length: 89

Access DeniedAccess Denied

Not sure why I see different behaviour because from what I can see the response is the same.

Appreciate any thoughts.

Simon