search

berkshelf / ridley

A reliable Chef API client with a clean syntax
Other
231 stars 85 forks source link

Ridley does not use Faraday middleware for following redirects #301

Open trekr5 opened 9 years ago

trekr5 commented 9 years ago

Hi,

I'm using the ridley gem to find a data-bag on a chef server and receive the following response:

Ridley::Errors::HTTPMovedPermanently:

301 Moved Permanently

301 Moved Permanently

nginx/1.4.4

After instantiating the Ridley client and creating a new object, this is how I try to find a databag named aws-admin:-

data = ridley.data_bag.find("aws-admin").

There is nothing in the response that I receive that gives me any information about a new location. (I have confirmed that this databag does exist on the chef server).

Can anyone give me some advice on how to solve this problem?

Thanks

reset commented 9 years ago

@trekr5 looks like we're not leveraging any middleware for following redirects. You can temporarily fix this in your NGINX config to avoid redirecting requests to Chef.

cbreden commented 9 years ago

I think I might be running into this same issue though the embedded ridley/faraday calls in a Vagrant run. I'm not very familiar with nginx configurations -- is there anything you'd recommend changing in the standard embedded nginx config that's shipping with Chef?

vagrant log: https://gist.github.com/cbreden/0e454c3e302bc76cf5b1 chef nginx configs: https://gist.github.com/cbreden/3a733934590bcee2c41e