Re: Redirects continued -- was: Problem with certificate on home-grown WebID

Ok. Your problem should be fixed now. It turns out that the culprit was not redirects, which the apache
library I used does by default, but that I was misinterpreting your mime type.

    2.19 -            case Some(mime) => Lang(mime) getOrElse Lang.default
    2.20 +            case Some(mime) => {
    2.21 +              Lang(mime.split(";")(0)) getOrElse Lang.default
    2.22 +            }

I had to split after the ";" so that Jena could know the right mime type to interpret
the content.

Henry

On 21 Dec 2011, at 18:20, Pierre-Antoine Champin wrote:

> On 12/21/2011 05:19 PM, Henry Story wrote:
>> 
>> On 21 Dec 2011, at 16:57, Pierre-Antoine Champin wrote:
>> 
>>> Hi,
>>> 
>>> I had the same misunderstanding as Sebastian, creating WebID
>>> http://champin.net/pa
>>> 
>>> I now created
>>> http://champin.net/#pa
>>> (which I too prefer, btw).
>>> 
>>> But that one does not work with foafssl.org :-(
>> 
>> That's because at present it does not have redirection implemented and you resource redirects
>> 
>> $ curl -i  http://champin.net/ 
>> HTTP/1.0 302 Found
>> Server: BaseHTTP/0.3 Python/2.5.2
>> Date: Wed, 21 Dec 2011 16:15:10 GMT
>> Location: http://liris.cnrs.fr/~pchampin/
>> Content-type: text/html
>> Vary: Host
> 
> 
> I beg to differ: http://champin.net/pa redirected as well, and it worked
> (and still does)!

Social Web Architect
http://bblfish.net/