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.

Sign up for GitHub

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

Jump to bottom

Kill blocked adbusters #1

Open
mjangda opened this issue Oct 30, 2013 · 3 comments
Open

Kill blocked adbusters #1

mjangda opened this issue Oct 30, 2013 · 3 comments

Comments

@mjangda
Copy link
Member

mjangda commented Oct 30, 2013

For any known adbusters that we've nixed, we should serve a nice 403 page :)
@paulgibbs
Copy link
Contributor

Is there any disadvantage to these ad vendors if we return a 403 instead of a 404, or any advantage to us?

@mjangda
Copy link
Member Author

mjangda commented Nov 26, 2013

No advantage either way as long as we wp_die()

@natebot natebot mentioned this issue Dec 27, 2013
Closed
@natebot
Copy link
Contributor

natebot commented Nov 8, 2014

Is this still an issue? I'm wondering why 403 is the right signal to send. Isn't it the case those resources are not to be found, and not just forbidden to be accessed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@natebot @mjangda @paulgibbs