Jump to content

Protocol Filtering Issue


Recommended Posts

I have an issue with logging in to one specific site when protocol filtering is enabled. I enabled developer mode in Chrome to troubleshoot and see this error:

Access to XMLHttpRequest at 'https://raptv.umsgw.quickplay.com/qp/login?lang=en' from origin 'https://rogersanyplacetv.com' has been blocked by CORS policy: Request header field x-authorization is not allowed by Access-Control-Allow-Headers in preflight response.

Further details:

1) ESET NOD32 v12.0.31.0
2) This issue started about 7 days ago
3) Disabling protocol filtering allows the login request to proceed as expected


Is it possible that the protocol filtering mechanism is blocking the login request in error?

Link to comment
Share on other sites

Do a Google search using this: "access to xmlhttprequest at from origin has been blocked by cors policy". Appears it's a security issue with the web site you mentioned.

Why Eset protocol filtering would trigger it, I really don't have a clue. You can always exclude that web site from protocol filtering at your own risk.

Edited by itman
Link to comment
Share on other sites

  • Most Valued Members

As above , the problem seems related to the code on the site itself and not anything that protocol filtering is causing.

In Firefox a completely different message is returned from the site/server (Not ESET)  ...

" The requested URL was rejected. Please consult with your administrator.

Your support ID is: 3096220045441371025"


Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...