Jump to content

LBates

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Thanks Andre. Is there an ETA for the next update? Lawrence Bates | Sr. DevOps Engineer – InfoSpace LLC lawrence.bates@infospace.com | +1.425.709.8122
  2. Typo: that should read "it's not the AWS CDN IP addresses themselves that are blocked"
  3. To clarify, it's not the AWS CDN IP addresses themselves that aren't blocked, it's anything that references *.inspsearchapi.com, which is used to serve content to pages. Adding *.inspsearchapi.com to "Web Exclusions" in Malwarebytes Anti-Malware allows content and search results to be returned and displayed as expected. Lawrence Bates | Sr. DevOps Engineer – InfoSpace LLC lawrence.bates@infospace.com | +1.425.709.8122
  4. My company is receiving complaints from users who are seeing issues with search results and content being blocked by Malwarebytes Anti-Malware, specifically the Real-Time Protection module in the Premium edition: Detection, 9/10/2015 2:26 PM, SYSTEM, W8E209013, Protection, Malicious Website Protection, Domain, 54.230.140.57, csr.inspsearchapi.com, 26933, Outbound, C:\Program Files (x86)\Internet Explorer\iexplore.exe, The IP addresses being blocked are part of the range used by our Amazon CloudFront CDN and so all of our hosted and partner sites that are being served content from the CDN are not returning results and/or have missing content and images. This can be reproduced by browsing to ​hxxp://search.pch.com and entering a search term (i.e. "Tigers"). The site appears to be blocked and no results are returned. Another example is hxxp://www.dogpile.com where images and content are not shown. Any assistance resolving this issue in a timely manner would be greatly appreciated. Thanks. Lawrence Bates | Sr. DevOps Engineer – InfoSpace LLC lawrence.bates@infospace.com | +1.425.709.8122
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.