Url Grey v 0.1.3 release notes# 16 Jun 2017 by Sean
New in release 0.1.3
This release protects the application’s domain from being redirected to by the app to avoid possible infinite loops or inaccessible application routes.
To accomplish this, the following changes were made:
- A new custom validator,
- An additional validation was added to the
The validator could easily be extended to check requested redirect targets against an array of blacklisted domains, rather than just the application domain. I have no need for this personally, but it’s worth noting as it could be useful to others.
The big learn
The Addressable gem saved a lot of hackwork on this one. The validator needed to be able to assess redirects with and without schemes (schemes are prepended
before_validation), which Ruby’s inbuilt
URI has difficulty with:
URI doesn’t parse the unqualified URL.
Addressable::URI.heuristic_parse('www.google.com'), the return object is fully qualified and will respond to the
Once that was in place, checking against the application’s host (set in
application.rb) was easy. There was a while where I ran around in circles trying to get Rails to see it’s own address, but because of the reverse-proxied architecture in production and staging, it just kept returning meaningless values. The workaround would be to make an actual HTTP request externally and see what the response says about ourselves… but that could take for ever. Faster to just tell the app who/where it is.
This site has turned off cross-site user tracking for Disqus, as much as is possible. If you want to know more about it, Afterpad has a decent post about it, explaining what is tracked, and what a site opting out means.