Skip to content

Conversation

@miyucy
Copy link
Contributor

@miyucy miyucy commented May 4, 2019

Follow up to #647

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@estolfo
Copy link
Contributor

estolfo commented May 6, 2019

thanks @miyucy !

@estolfo estolfo merged commit 178a343 into elastic:master May 6, 2019
@yaauie
Copy link
Member

yaauie commented May 6, 2019

Unfortunately this introduced a new bug; when the port is specified explicitly, and the port is the same as the default port for the given scheme (e.g., http://foo.com:80/, https://foo.com:443/), we ignore it and end up routing to 9200 instead.

I've opened a new PR here: #651

@miyucy
Copy link
Contributor Author

miyucy commented May 7, 2019

@yaauie ah. I didn't thought that cases. Thanks for follow up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants