Broken set_routes using query_request?

[coleshaw]

I'm seeing weird behavior locally with EtnaClient not being able to find the route definitions on Metis stage. I suspect it is because I changed query_request to use uri.request_uri instead of the old uri.path. This makes the OPTIONS request /?, which means no routes are returned by the Etna middleware in Metis.

From: /home/developer/.rbenv/versions/2.5.7/lib/ruby/gems/2.5.0/gems/etna-0.1.14/lib/etna/client.rb:97 Etna::Client#query_request:

    94: def query_request(type, endpoint, params={}, &block)
    95:   uri = request_uri(endpoint)
    96:   uri.query = URI.encode_www_form(params)
 => 97:   req = type.new(uri.request_uri, request_params)
    98:   request(uri, req, &block)
    99: end

[5] pry(#<Etna::Client>)> uri.request_uri
=> "/?"
[7] pry(#<Etna::Client>)> uri.path
=> "/"

I wonder if either options() should use a non-query request, or we should just make sure no trailing ? is present on a query_request with no params.

[coleshaw]

Seems to work -- with a valid token! Something in the middleware must account for this already...