Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 5 subscribers
  • Views 1943 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM 9.7 Web filter Nest Camera "Invalid HTTP method"

Michael Gaboury

Good day All,

This is my first post to this community and I would like to thank you all for your contributions and time. 

I have recently installed UTM 9.7 at home and almost everything is functioning as expected. The only kink so far is with web filtering and my Nest camera web interface that stops functioning when web filtering is enabled.

There was a post here that spoke on this topic but terminated last year and is now locked. My issues are the same as others so my intention is to find out if there is a fix in the works or are we all doomed.

Recap:

Nest camera works as expected with web filtering turned off, but when web filtering turned on the nest camera web interface stops working (In any browser I tested). I have whitelisted the Nest URI (in filtering options) and now I just get the following output:

2020:11:15-12:57:19 sophos_utm httpproxy[7311]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="http_parser_context_execute" file="http_parser_context.c" line="97" message="Unable to parse a http message of 517 bytes (HPE_INVALID_METHOD: invalid HTTP method)"
2020:11:15-12:57:19 sophos_utm httpproxy[7311]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xd9bd4300" function="read_request_headers" file="request.c" line="1615" message="unable to parse a http message on handler 147 (Resource temporarily unavailable)"
Here is a screenshot from my web filtering options:
So, in a nut shell, I would just like to know if this issue is going to be fixed in the future as I have seen posts related to this subject that go back many years. Thanks for your time!
Cheers,
Mike



This thread was automatically locked due to age.
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community! 

    Did you configure web filtering operation mode in transparent mode? If yes, try to bypass the destination domains under Web Protection > Filtering Options > Misc > Skip Transparent Mode Destination hosts/networks and let us know if that resolves your issue. 

    Thanks,

  • 0

    Hello, thank you for your reply.

    I have tried that previously and was unsucsessful, I will try again. This time I will get the full gambit of IP's that I whitelisted in filtering options > exeptions.

    I will update when completed.

    Thanks again!

    Mike

  • +1

    So, I found a elegant solution to my problem, I employed a VPN for the clients using the nest web interface and I can now use the web filtering features of UTM 9! 

    Thanks for you help Harsh!

    Cheers,

    Mike

Unfiltered HTML