Skip to content
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

Closed
atomGit opened this issue Oct 10, 2017 · 6 comments
Closed

[Neat URL v3.1.0] clarification regarding URL request types #53

atomGit opened this issue Oct 10, 2017 · 6 comments
Labels

Comments

@atomGit
Copy link

atomGit commented Oct 10, 2017

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 :)

@Smile4ever
Copy link
Owner

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
I have set "doubtful" when I think it's not worth it

To answer your question:

beacon

  • Requests sent through the Beacon API.
  • Useful

csp_report

  • Requests sent to the report-uri given in the Content-Security-Policy header, when an attempt to violate the policy is detected.
  • Doubtful

font

  • Web fonts loaded for a @font-face CSS rule.
  • Doubtful

image

  • Resources loaded to be rendered as image, except for imageset on browsers that support that type (see browser compatibility below).
  • Doubtful

imageset

  • Images loaded by a picture element or given in an img element's srcset attribute.
  • Doubtful

main_frame

  • Top-level documents loaded into a tab.
  • Useful (default)

media

  • Resources loaded by a video or audio element.
  • Doubtful

object

  • Resources loaded by an object or embed element.
  • Browsers that don't have a dedicated object_subrequest type (see browser compatibility below), also label subsequent requests sent by the plugin as object.
  • Doubtful

object_subrequest

  • Requests sent by plugins.
  • Doubtful

ping

  • Requests sent to the URL given in a hyperlink's ping attribute, when the hyperlink is followed.
    *Browsers that don't have a dedicated beacon type (see browser compatibility below), also label requests sent through the Beacon API as ping.
  • Useful

script

  • Code that is loaded to be executed by a <script> element or running in a Worker.
  • Doubtful

stylesheet

  • CSS stylesheets loaded to describe the representation of a document.
  • Doubtful

sub_frame

  • Documents loaded into an <iframe> or element.
  • Useful

web_manifest

  • Web App Manifests loaded for websites that can be installed to the homescreen.
  • Doubtful

websocket

  • Requests initiating a connection to a server through the WebSocket API.
  • Doubtful

xbl

  • XBL bindings loaded to extend the behavior of elements in a document.
  • Doubtful

xml_dtd

  • DTDs loaded for an XML document.
  • Doubtful

xmlhttprequest

  • Requests sent by an XMLHttpRequest object or through the Fetch API.
  • Doubtful

xslt

  • XSLT stylesheets loaded for transforming an XML document.
  • Doubtful

other

  • Resources that aren't covered by any other available type.
  • Maybe

btw, i like the content on your website - you seem to be pretty busy and knowledgeable for a young fella :)

Thank you.

@atomGit
Copy link
Author

atomGit commented Oct 10, 2017

perfect - thanks - hopefully helpful to others as well
i'll go with all those you marked "useful"

@atomGit atomGit closed this as completed Oct 10, 2017
@atomGit
Copy link
Author

atomGit commented Oct 10, 2017

one more thing ... you might want to add that to your wiki and/or your AMO page maybe?

@atomGit atomGit reopened this Oct 10, 2017
@Smile4ever
Copy link
Owner

@crssi
Copy link

crssi commented Oct 13, 2017

Over image and xmlhttprequest all kind of shit load is calling back.

For example:
maps.google.com, youtube over XHR
youtube, facebook over IMG

@Smile4ever
Copy link
Owner

I've edited the wiki page to reflect that.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants