nak admin is sending wrong "u" tag

[alexgleason]

It's sending the url without the slash [ "u", "http://localhost:8000" ]

The correct tag is [ "u", "http://localhost:8000/" ] (with slash)

[fiatjaf]

Why do you say that? I think the correct is without the slash, according to RFC7235. Or at least I saw it somewhere when implementing this.

[alexgleason]

Relays are URLs. URLs must have a path. Without the path it is an "origin" not a full URL. I worked around this by normalizing both URLs before comparing in my nip98 implementation

[fiatjaf]

Your reasoning makes total sense, but it is worthless if we're just following an arbitrary standard that says URLs with an empty path should be rendered without a trailing slash.

I was under the impression the standard specified in NIP-98 says the URLs should not have a trailing slash, but I would be happy to be proven wrong.

Now I can't find this information anywhere.

[alexgleason]

It's because of this:

> new URL("https://example.com").href
"https://example.com/"

Also, "https://example.com/relay" is not the same URL as "https://example.com/relay/" and could actually be a completely different relay

[fiatjaf]

I know, but https://example.com is the same as https://example.com/.

Do you know if new URL("https://example.com").href is following RFC7235?

[alexgleason]

I don't know, but I am very convinced it's wrong. I'm hitting the same issue in Elixir. URLs have paths.

[alexgleason]

RFC7235 talks a lot about origins, but the "u" tag is a full URL

[fiatjaf]

It was stupid to reference an RFC in NIP-98 in the first place instead of just saying what the URL looks like. Specially given that the referenced RFC does not say how paths should be rendered.

We must clarify that in the NIP. I'm fine either way, we should just go with what the majority of software is doing at this point.