Is this bug going to be fixed, or it has become a feature with a workaround?
Workaround
BUG reason="HTTP parsing error encountered."
BUG reason="HTTP pipelined request encountered."
This thread was automatically locked due to age.
Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.
Is this bug going to be fixed, or it has become a feature with a workaround?
Workaround
BUG reason="HTTP parsing error encountered."
BUG reason="HTTP pipelined request encountered."
Trying to reproduce the issue with MICROSOFT_DEVICE_METADATA_RETRIEVAL_CLIENT, I see similar requests from Windows machines on my network but they are never getting blocked or logged as pipelined.
The requests to go.microsoft.com/fwlink/... always gets a status_code="302" response - a redirection.
They are always followed in the log by a request to dmd.metaservices.microsoft.com
There is then another request to go.microsoft.com/fwlink/... but this always seems to come over a new TCP connection (it has a different source port), so it cannot be Pipelined.
Perhaps you could take a look in the detailed log viewer and filter it on "go.microsoft.com". It would be interesting to see (a) how often these requests are blocked as Pipelined, and (b) if there are requests logged immediately after or before the 'blocked' ones that might give us some hints as to why some are OK and some not.
Thank you for your support.
(a) "HTTP pipelined request encountered." was 1/64.
(b) There was no access from the same source port.
And Denied with reason="" was 18/64.
When is this? Is this related?
Hello, I used the v18.0 MR4
here are 2 popular examples