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

Suggestion: Show actually parsed URL #29

Open
jneubert opened this issue Sep 16, 2015 · 2 comments
Open

Suggestion: Show actually parsed URL #29

jneubert opened this issue Sep 16, 2015 · 2 comments

Comments

@jneubert
Copy link

It could be helpful for users to show the actually parsed URL (which may be different from the user input when content negotiation is involved - see e.g. #28) as part of the page.

@gkellogg
Copy link
Member

It should be able to show the final URL after redirections. At one time, it actually showed the parser(s) used to extract the data as well. Note that http://rdf.greggkellogg.net/distiller uses essentially the same parser, and it does indicate the parser used as a result of content-negotiation.

@gkellogg
Copy link
Member

gkellogg commented Oct 6, 2015

Unfortunately, no good way to show the redirected URL without hacking some internals. I'll leave this open for future consideration as we work on RDF.rb 2.0.

I did make it so the reader used is shown in the UI, which I'll release shortly.

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

No branches or pull requests

2 participants