Kingsley, On 19 Feb 2008, at 20:48, Kingsley Idehen wrote:
> Richard Cyganiak wrote: >> Kingsley, Zdravko, >> >> It turns out that all DBpedia category URIs are broken since the >> server move from FU to OpenLink. Example: >> >> $ curl -I http://dbpedia.org/resource/Category:Berlin >> HTTP/1.1 303 See Other >> Server: Virtuoso/05.00.3023 (Solaris) x86_64-sun-solaris2.10-64 VDB >> Connection: close >> Content-Type: text/html; charset=UTF-8 >> Date: Tue, 19 Feb 2008 18:23:00 GMT >> Accept-Ranges: bytes >> Location: /page/Category%3ABerlin >> Content-Length: 0 >> >> Note that the redirect goes from </resource/Category:Berlin> to >> </page/Category%3ABerlin>. The ":" character has been %-encoded >> somewhere in the process. This sends the client into a 404 because >> </page/Category%3ABerlin> does not exist. It should be >> </page/Category:Berlin>. >> >> The problem is only in the redirect; the target at >> http://dbpedia.org/page/Category:Berlin works fine. >> >> I don't know why this happens. >> >> (Just one thing to look into: Pubby has a configuration option >> "conf:fixUnescapedCharacters", whose value is a list of characters to >> be %-encoded in the redirect. We needed this option to work around a >> quirk in Apache in reverse proxy mode. But the Pubby config file I've >> sent you doesn't have the ":" character in the list, so I don't know >> if this configuration option has anything to do with it.) >> >> Can you please look into this? >> >> Richard >> > Richard, > > The current DBpedia 3.0 release is in "hot staging" mode right now. > Thus, if it is too broken we will revert back to the prior release and > then re-stage DBpedia 3.0 on a different server for further testing. > > I will give the current instance another 24-48 hours re. testing and > fixing before reverting back if need be. I believe the issue above is unrelated to the dataset, but caused by some Pubby/Virtuoso interaction and has most likely been present ever since we moved servers from Berlin to Burlington. If possible, let's push ahead and fix the last remaining glitches. I also think it's acceptable to leave this particular issue unresolved for a few days, it shouldn't affect too many users and is not highest priority. I would prefer this over having to revert to an older version or server. Richard > > > > -- > > > Regards, > > Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen > President & CEO > OpenLink Software Web: http://www.openlinksw.com > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Dbpedia-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
