You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my setup, Elastic is proxied by an Apache HTTP to some subfolder. So basically instead of somedomain.com the instance is listening on somedomain.com/elastic It uses the standard HTTP port 80. As long as I connect via HTTP requests directly, everything works well, but the problems start, when trying to connect via PHP.
I finally got it to work using the simple URL http://somedomain.com:80/elastic.
I think, that the extended host configuration should cover cases, where a path is involved by introducing another path property there, which would also be in line with the referenced parse_url() output.
Code snippet of problem
To investigate the errors I used the following code
Seems reasonable to me. I'm a bit short on cycles at the moment, not sure when I'll get to this. If you'd like to send a PR I'd be happy to review it, otherwise I'll try to get to this enhancement soonish :)
Sorry for the pain that you had to go through to get that working!
Turns out I was not trying hard enough. path is actually a supported property (don't know why I didn't try that as well).
Submitted a pull request, so that the list of possible parameters for the extended host configuration is explicitly referenced in the docs by a pointer to the respective PHP docs on parse_url().
Summary of problem or feature request
In my setup, Elastic is proxied by an Apache HTTP to some subfolder. So basically instead of
somedomain.com
the instance is listening onsomedomain.com/elastic
It uses the standard HTTP port 80. As long as I connect via HTTP requests directly, everything works well, but the problems start, when trying to connect via PHP.The Extended Host Configuration section in the documentation does not cover this case. So I tried different options as follows to no avail:
http://somedomain.com/elastic
http://somedomain.com:9200/elastic/_stats
[ "host" => "vis.inf-bb.uni-jena.de/es", "scheme" => "http", "port" => "80" ]
http://somedomain.com/elastic:80/_stats
I finally got it to work using the simple URL
http://somedomain.com:80/elastic
.I think, that the extended host configuration should cover cases, where a path is involved by introducing another
path
property there, which would also be in line with the referencedparse_url()
output.Code snippet of problem
To investigate the errors I used the following code
System details
The text was updated successfully, but these errors were encountered: