Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

validateUrl: Increasing valid TLD length to 63 #115

Conversation

systemizer
Copy link
Contributor

@systemizer systemizer commented Jan 17, 2020

According to RFC1035 (https://tools.ietf.org/html/rfc1035), the maximum size of a label is 63 octets.

We need this increased because we use a TLD that is larger than 4 characters. We cannot setup alerts as a result.

Description of changes:
This updates the validateUrl function to accept urls with TLDs up to 63 octets (consist with the RFC1035)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

According to RFC1035 (https://tools.ietf.org/html/rfc1035), the maximum size of a label is 63 octets.

We need this increased because we use a domain that is larger than 4 characters. We cannot setup alerts as a result.
@dbbaughe
Copy link
Contributor

Thanks @systemizer,

Could you add a quick unit test to make sure we don't regress in the future :)

@dbbaughe dbbaughe merged commit 4db93f3 into opendistro-for-elasticsearch:master Jan 17, 2020
@dbbaughe
Copy link
Contributor

Thanks @systemizer !

ylwu-amzn added a commit to ylwu-amzn/alerting-kibana-plugin that referenced this pull request May 5, 2020
…csearch#115)

* Increasing valid TLD length to 63

According to RFC1035 (https://tools.ietf.org/html/rfc1035), the maximum size of a label is 63 octets.

We need this increased because we use a domain that is larger than 4 characters. We cannot setup alerts as a result.

* Add validateUrl test for TLD with >4 characters

* Adding validateUrl test for TLD with >63 characters
ylwu-amzn added a commit that referenced this pull request May 5, 2020
* validateUrl: Increasing valid TLD length to 63 (#115)

* Increasing valid TLD length to 63

According to RFC1035 (https://tools.ietf.org/html/rfc1035), the maximum size of a label is 63 octets.

We need this increased because we use a domain that is larger than 4 characters. We cannot setup alerts as a result.

* Add validateUrl test for TLD with >4 characters

* Adding validateUrl test for TLD with >63 characters

* anomaly detection changes. (#123)

* anomaly detection changes.

Co-authored-by: mihirsoni <[email protected]>

* remove anomaly detector option when create monitor if AD plugin not installed

* address comments: copyright, remove unused code,etc

* remove extra showLoader

Co-authored-by: mihirsoni <[email protected]>

* change words and padding according to ux review comments (#132)

* change words and padding according to ux review comments

* fix padding of monitor schedule

* rename monitor method description according to UX review comments (#133)

* fix snapshot test and validate unit test

Co-authored-by: mihirsoni <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants