Julian Figueroa

@karmi your sample works: ``` ➜ go run ./test/test_elastic.go PUT http://localhost:9200/test/_doc/fôô?refresh=true 201 Created 458ms GET http://localhost:9200/t*/_search?pretty=true 200 OK 59ms [200 OK] {some json} ``` What do you suggest? Waiting for...

Thanks!!, I've run it also with the logger on, locally on my machine and I can see the `index-pattern-*` in the URL, so I assume it should be an issue...

Sorry, I kept testing and checked the logger in deep, and still found issues. It really depends on the logger. `Color`, `Curl` and `JSON` loggers use `req.URL.Path` which logs `*`,...

Yes, seems to be elastic is able to handle both: ``` curl http://localhost:9200/t*/_search?pretty curl http://localhost:9200/t%2A/_search?pretty ``` and return successful results. I guess the bottom question is, Should the library (or...

I think there should be a way to allow certain characters in the index part of the path. For example, Java or JS url encode doesn't encode the `*` and...

Sure, I understand the code you posted returns correct results, and that's because elasticsearch server is able to handle indexes in the URL both `like-this-*` and `like-this-%2A`. We've established the...

It can be a small detail, but it makes the server logs more readable and also allows us to put controls in place for more restrictive URLs that explicitly use...

@traviskochel Hey thanks for the recommendation. Any short guide on how to migrate? Because their README has basically the same guide of installation, so, it would be just changing the...

@sergeykish This repo seems really inactive. Any thoughts on mantaining your own version with Rails 5 deprecation cleanup, and 5.1 support?

@lostboy glad you're back. I've checked this in depth couple of months ago, and I've found one fork that has been mantained and updated to work with Rails 5: https://github.com/davidakachaos/workless_revived...