cygri/pubby — Issue #5: missing URL encoding ?
Author: dr0ide
Created: 2012-01-04 13:01:01+00:00
State: open

first: a happy new year !

I experienced some problems with pubby, stable release Pubby 0.3.3 .
Indexing some stuff to my triple store a space in a URI is URL-encoded correctly into a '+'. , i.e. like this:

@prefix frbr: .
@prefix rdf: .

rdf:type frbr:Item .

This resource is linked with an other resource in pubby. When I click in pubby to follow that link I got a "404 Not Found".
But its working SPARQling 4store directly.

Something similar with url-encoded '/' (which is then a %2F). Following that link in pubby brings up a "[an error occurred while processing this directive]" which seems to be because the %2F is internally re-interpreted as an '/' .
(see http://lobid.org/resource/HT002511874 , under frbr:exemplar )
Using 4store as backend, and querying this resource in 4store directly using SPARQL _does_ work (naturally only if I "curl --data-urlencode" the query) .
Again, its working SPARQling 4store directly.

Another problem is with ':' , if I urlencode it pubby doesnot made correct links - if the colon is left decoded pubby works.

Could it be that pubby follows (internal) URIs without --data-urlencode it , or am I doing something wrong?

-o