join.me and logme.in connections fail with explicit proxy deployment

book

Article ID: 166683

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

 Users are unable to access join.me and logme.in through an explicit proxy deployment.

Resolution

join.me and logme.in do not fuction well if protocol detection is enabled on explicit proxy deployment. by disabling protocol detection for the following URLs will allow it work.

define condition JoinMe_no_Proto_detect
    url.domain=logmein.com
    url.domain=logmeinrescue.com
    url.domain=logmeinrescue-enterprise.com
    url.domain=logme.in
    url.domain=hamachi.cc
    url.domain=internapcdn.net
    url.domain=LogMeIn123.com
    url.domain=123rescue.com
    url.domain=support.me
    url.domain=join.me
    url.domain=cub.by
    url.domain=cubby.com
end

<Proxy JoinMe_no_Proto_detect> condition=JoinMe_no_Proto_detect
   http.method=CONNECT detect_protocol(no) authenticate(no) ALLOW

 

the URLs can be confirmed from LogMeIn website on Whitelisting and LogMeIn page
http://help.logmein.com/selfserviceknowledgerenderer?type=FAQ&id=kA030000000FdVqCAK