On 0.12.3, I was trying to decode a json+ld with
"@context": "https://schema.org"
So I added the following to jarcache.json
{
"Content-Location": "http://schema.org",
"X-Classpath": "jsonldcontext.json",
"Content-Type": "application/ld+json"
}
This did not work as expected, the cache was not used. After odious debugging I found the cache was searched with the port number added, so I could produce a cache hit only with the following entry:
{
"Content-Location": "https://schema.org:443/",
"X-Classpath": "jsonldcontext.json",
"Content-Type": "application/ld+json"
}
This is certainly unexpected. Why rewrite the URL before cache lookup? Also the documentation suggests, that the port number is not necessary. Please fix this.
Reactions are currently unavailable
On 0.12.3, I was trying to decode a json+ld with
So I added the following to jarcache.json
{ "Content-Location": "http://schema.org", "X-Classpath": "jsonldcontext.json", "Content-Type": "application/ld+json" }This did not work as expected, the cache was not used. After odious debugging I found the cache was searched with the port number added, so I could produce a cache hit only with the following entry:
{ "Content-Location": "https://schema.org:443/", "X-Classpath": "jsonldcontext.json", "Content-Type": "application/ld+json" }This is certainly unexpected. Why rewrite the URL before cache lookup? Also the documentation suggests, that the port number is not necessary. Please fix this.