Skip to content

Fixed redirect errors (301) on 3 domains #353

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

Closed
wants to merge 4 commits into from
Closed

Fixed redirect errors (301) on 3 domains #353

wants to merge 4 commits into from

Conversation

AchoArnold
Copy link
Contributor

This fixes the redirect errors on the links below such that

http://twitter.com* becomes **https://twitter.com
http://www.packtpub.com
becomes **https://www.packtpub.com
http://www.flickr.com
becomes **https://www.flickr.com

This PR is meant to fix all the present errors reported on the latest build for the http://code.jquery.com/ website

@gnarf
Copy link
Member

gnarf commented Apr 3, 2015

I'm 👍 here - thanks for doing this!

@arschmitz
Copy link
Member

@najela huge thanks for working on all these. Making all the time i put into making spider.js worth it!

@AchoArnold
Copy link
Contributor Author

@arschmitz I would enjoy seeing code for the crawler which does this checks. Please where is it found?

@arthurvr
Copy link
Member

arthurvr commented Apr 4, 2015

Thanks for doing this! The code for spider lives in this repo: https://github.com/arschmitz/spider.js. I'm on mobile at the moment but will merge once I get a chance. Thanks!

@arschmitz
Copy link
Member

@arthurvr Thanks for posting the link just saw this. @najela there is also a grunt task for it https://github.com/arschmitz/grunt-spider ( though i need to update the documentation for it to match latest spider.js )

@@ -17,7 +17,7 @@
* Contact
* -------------------------------------------------------
* Email: dave@davegandy.com
* Twitter: http://twitter.com/fortaweso_me
* Twitter: https://twitter.com/fortaweso_me
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't be changing vendor files IMHO

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I buy your idea 💯/💯. Such errors will also not get noticed by jenkins

@AchoArnold
Copy link
Contributor Author

9567adf Solves the raised issues. I now understand why submitting a PR from your master branch is a bad idea :)

@arschmitz
Copy link
Member

@najela you don't need to worry about jenkins for errors in the 3rd party files we can configure ignore params for any of the jobs to fix things like this. Just let me know what ever needs to be ignored and ill configure it.

@arthurvr arthurvr closed this in aa7a240 Apr 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants