Repository navigation
Create directory on system without decoding encoded values in Slug #422
Description
Perhaps the title can be better with less assumptions as to what may be happening. Here is the code that I've used:
var options = {};
var url = 'https://example.org/';
var contentType = 'text/turtle';
var links = '<http://www.w3.org/ns/ldp#Container>; rel="type"';
var slug = encodeURIComponent('http://csarven.ca/foo');
var data = '';
var http = new XMLHttpRequest();
http.open('POST', url);
http.setRequestHeader('Content-Type', contentType);
http.setRequestHeader('Link', links);
if (slug && slug.length > 0) {
http.setRequestHeader('Slug', slug);
}
if (!options.noCredentials) {
http.withCredentials = true;
}
http.onreadystatechange = function() {
if (this.readyState == this.DONE) {
console.log(this);
}
};
http.send(data);Response has Location: /http%3A%2F%2Fcsarven.ca%2Ffoo.
What's physically created on the system is directory http: with subdirectory csarven.ca with file foo
Expected directory: http%3A%2F%2Fcsarven.ca%2Ffoo
This should be analogous to mkdir "http%3A%2F%2Fcsarven.ca%2Ffoo"
Metadata
Metadata
Assignees
Labels
No labels
Activity
csarven commentedon Jul 29, 2016
Oh there is more:
If I
mkdir http%3A%2F%2Fcsarven.ca%2Ffooand then later POST to that directory, the POST goes through (i.e., it creates say resourcehttps://example.org/http%3A%2F%2Fcsarven.ca%2Ffoo/bar). However, when I GET that container (http://example.org/http%3A%2F%2Fcsarven.ca%2Ffoo), it hasldp:contains <http://example.org/bar>. Expected:ldp:contains <http://example.org/http%3A%2F%2Fcsarven.ca%2Ffoo/bar>dmitrizagidulin commentedon Jul 29, 2016
Thanks, Sarven, that's helpful.
Fix handling/url-encoding of container names
Fix handling/url-encoding of container names (#469)
dmitrizagidulin commentedon Dec 7, 2016
Fixed in PR #469, closing.