-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Neat URL v3.1.0] clarification regarding URL request types #53
Comments
You can probably add most of the request types below without being annoyed every day. You can ask for every issue you encounter to investigate so I can look if this is something Neat URL should know about. I have set "useful" when it's likely to contain some kind of (tracking) mess To answer your question: beacon
csp_report
font
image
imageset
main_frame
media
object
object_subrequest
ping
script
stylesheet
sub_frame
web_manifest
websocket
xbl
xml_dtd
xmlhttprequest
xslt
other
Thank you. |
perfect - thanks - hopefully helpful to others as well |
one more thing ... you might want to add that to your wiki and/or your AMO page maybe? |
Over image and xmlhttprequest all kind of shit load is calling back. For example: |
I've edited the wiki page to reflect that. |
the addition of allowing the user to decide what request types are filtered is interesting, except i don't know what the heck to do with it :)
in your opinion, and given i'm concerned with privacy (i use the ghacks user.js in combo with my own) but am willing to sacrifice a bit of privacy for a somewhat carefree browsing experience, what request types should be filtered? in other words, what filters are unlikely to cause a lot of breakage? i don't mind fiddling around with some sites on occasion to get them to work, but i don't want to be constantly bothered with it
btw, i like the content on your website - you seem to be pretty busy and knowledgeable for a young fella :)
The text was updated successfully, but these errors were encountered: