RFC 1034 #65
Closed
RFC 1034 #65
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
|
Thanks! This repo hasn't been updated in a long time. which Domain has 24 characters? That's so crazy. I will update the source code REGEX to remedy this. |
Author
|
Yeah, I had no idea too. I googled after a bug report today (thanks Merlin). |
Author
|
I don't think we need a regex change other than this, as there's still a character limit of 63 according to the RFC i mentioned. I think this change will suffice. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Newer top-level domains such as ".network" triggered errors. 24 characters are currently the highest right now, but for future-readiness used 63 as per RFC 1034.