dots in the user name #49

Open
opened 4 months ago by schorsch · 4 comments

When visiting the page for https://codeberg.org/rene.schaar/pages I get the following errror:

image

Could the problem be the . in my username?

When visiting the page for https://codeberg.org/rene.schaar/pages I get the following errror: ![image](/attachments/25209456-6510-4246-ae22-da3d93472c72) Could the problem be the `.` in my username?
111 KiB
Collaborator

Yes it is. Please also see Codeberg/Community#561.

Yes it is. Please also see https://codeberg.org/Codeberg/Community/issues/561.
Poster

So to visit the website I would need to use https://pages.codeberg.org/rene.schaar/. But is there a way to configure a custom domain?

So to visit the website I would need to use https://pages.codeberg.org/rene.schaar/. But is there a way to configure a custom domain?
Collaborator

Not yet. Maybe it might be an idea to allow for other separators in the TXT records, so one can use

ALIAS / A+AAAA records for codeberg.page
TXT branch,repo.with.dot,user.with.dot,codeberg.page

or something like this? Unsure about the codeberg.page part as well as whether dot is a good separator, probably not (looks very confusing, maybe | is better, or +).

This issue would probably also arise for branches with dots in the name as well as repos, so having an alternative method at least for custom domains might be a good idea.

Not yet. Maybe it might be an idea to allow for other separators in the TXT records, so one can use `ALIAS` / `A+AAAA` records for codeberg.page `TXT branch,repo.with.dot,user.with.dot,codeberg.page` or something like this? Unsure about the codeberg.page part as well as whether dot is a good separator, probably not (looks very confusing, maybe `|` is better, or `+`). This issue would probably also arise for branches with dots in the name as well as repos, so having an alternative method at least for custom domains might be a good idea.
fnetX changed title from SSL_ERROR_BAD_CERT_DOMAIN to dots in the user name 4 months ago
Collaborator

It turns out that according to https://serverfault.com/a/928204, even a CNAME target doesn't have to be a hostname - that means that using a backslash as an escape character (CNAME rene\.schaar.codeberg.page) would be totally fine. There probably are some registrars who don't like that, but a TXT record would work in that case.

For *.codeberg.page, the only idea I have would be moving the dot up half a character (·) and then using Punycode for http://rene·schaar.codeberg.page/ (http://xn--reneschaar-v2a.codeberg.page/). But I'd probably rather just say that dots in usernames are unsupported for Codeberg Pages... It's really bad IMO that Gitea allows _, - and . in usernames, and even consecutively. So one couldn't even use __ to escape a dot in an URL :/

It turns out that according to https://serverfault.com/a/928204, even a CNAME target doesn't have to be a hostname - that means that using a backslash as an escape character (`CNAME rene\.schaar.codeberg.page`) would be totally fine. There probably are some registrars who don't like that, but a TXT record would work in that case. For `*.codeberg.page`, the only idea I have would be moving the dot up half a character (·) and then using Punycode for http://rene·schaar.codeberg.page/ (http://xn--reneschaar-v2a.codeberg.page/). But I'd probably rather just say that dots in usernames are unsupported for Codeberg Pages... It's really bad IMO that Gitea allows `_`, `-` and `.` in usernames, and even consecutively. So one couldn't even use `__` to escape a dot in an URL :/
momar added the
improvement
label 4 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.