link rel=meta sent twice (trivial, harmless)

[sandhawke]

Just FYI:

$ curl -v --cert keys/alicedemo.pem https://alicedemo.databox.me/
...
> GET / HTTP/1.1
> Host: alicedemo.databox.me
> User-Agent: curl/7.43.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Accept-Patch: application/json, application/sparql-update
< Accept-Post: text/turtle, application/json
< Access-Control-Allow-Credentials: true
< Access-Control-Expose-Headers: User, Location, Link, Vary, Last-Modified, WWW-Authenticate, Content-Length, Accept-Patch, Accept-Post, Allow, Updates-Via, Ms-Author-Via
< Access-Control-Max-Age: 1728000
< Allow: OPTIONS, HEAD, GET, PATCH, POST, PUT, MKCOL, DELETE, COPY, MOVE, LOCK, UNLOCK
< Content-Type: text/turtle
< Etag: "659fd97569a6012bf0b557068204ef0c"
< Link: <https://alicedemo.databox.me/,acl>; rel="acl", <https://alicedemo.databox.me/,meta>; rel="meta"
< Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"
< Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
< Link: <https://alicedemo.databox.me/,meta>; rel="meta"

Note that rel="meta" is in there twice.

[melvincarvalho]

Good catch, thanks for reporting this!

It would be great if we could encourage people that spot small issues like this, to feel empowered to dig into the code base, and maybe take the next step of submitting a patch.

@sandhawke do you think that might be something you'd like to have a go at?

[sandhawke]

No, I'm not coding go these days.