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

Armor against actually trash URLs #190

Closed
arrdem opened this Issue Mar 31, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@arrdem
Contributor

arrdem commented Mar 31, 2015

Ex.

The root of these various failures seems to be that the version part of the path is insufficiently validated. That should be pretty easy to fix up. Right now, the invalid version string causes an actual unhandled exception on the Grimoire side.

@arrdem arrdem added the enhancement label Mar 31, 2015

@arrdem arrdem modified the milestone: 0.4.16 Apr 1, 2015

@arrdem arrdem modified the milestones: 0.4.16, 0.4.17 Apr 26, 2015

@arrdem

This comment has been minimized.

Show comment
Hide comment
@arrdem

arrdem Dec 12, 2016

Contributor

I'm just gonna punt on this. Most of the 404s that Grimoire gets are from reeeeally stale old links which got broken by accident and are being visited by a crawler of some sort. The optimistic ones are users searching for documentation which I don't host (clojurescript) or newer versions (Clojure alpha builds) and in neither case is there really a sane way to recover.

Contributor

arrdem commented Dec 12, 2016

I'm just gonna punt on this. Most of the 404s that Grimoire gets are from reeeeally stale old links which got broken by accident and are being visited by a crawler of some sort. The optimistic ones are users searching for documentation which I don't host (clojurescript) or newer versions (Clojure alpha builds) and in neither case is there really a sane way to recover.

@arrdem arrdem closed this Dec 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment