Header location with POST return path and not url

[bourgeoa]

@csarven @michielbdejong @jeff-zucker
Doing tests with solid-rest we found that header location return path and I was expecting url.
What is the good content from spec viewpoint.

in https://github.com/solid/node-solid-server/blob/master/lib/handlers/post.js

  function one () {
    debug('Receving one file')
    const { slug, link, 'content-type': contentType } = req.headers
    const links = header.parseMetadataFromHeader(link)
    const mimeType = contentType ? contentType.replace(/\s*;.*/, '') : ''
    const extension = mimeType in extensions ? `.${extensions[mimeType][0]}` : ''

    ldp.post(req.hostname, containerPath, req,
      { slug, extension, container: links.isBasicContainer, contentType }).then(
      resourcePath => {
        debug('File stored in ' + resourcePath)
        header.addLinks(res, links)
        res.set('Location', resourcePath)
        res.sendStatus(201)
        next()
      },
      err => next(err))
  }

[bourgeoa]

@csarven What is the proper spec viewpoint ?
@jeff-zucker
I reopen this issue due to differences between NSS and CSS, see discussion in issue 0dataapp/hello#2

• CSS header location return absolute URL in conformance with rfc2616-sec14.30,
• but NSS header location return the relative url like in MDN fetch.

[bourgeoa]

@michielbdejong What do you think ? Does this imply a test-suite change ?

[csarven]

RFC 7231 obsoletes RFC 2616. RFC 7230/7231 uses Location = URI-reference referencing RFC 3986 and that can be an absolute or a relative reference.

[bourgeoa]

@csarven thanks for the response.
https://datatracker.ietf.org/doc/html/rfc7231#section-7.1.2

It is not so easy for app developer to imagine that location depends on server implementation.

We will have to update our solid-file-client library. jeff-zucker/solid-file-client#214

Anyway this closes the issue.