Bartosz Blimke
Bartosz Blimke
ok so is that related to `delete` request? In your first example you used `:get`
It's probably because the connection is opened before any request is made. WebMock can only intercept http requests by their pattern. You open a new connection at `conn = Faraday.new(:url...
sure, but the stubs are on http requests, not on https connections. request is stubbed by url pattern. connection only uses host, protocol and port. There can be multiple requests...
Can someone provide a failing code snippet to reproduce the issue?
wow, I never thought of that! nice :) This can be documented as long as we add an acceptance spec to cover that scenario and it passes across all supported...
@mikekelly WebMock tries to normalize headers to have unified version for comparison with stubs. What exactly is the issue you have problems with?
@mikekelly I see. You're right, WebMock should not do that.
It was added to ensure unified format of headers i.e. if case someone declares 'content_type' in the response.
It's wasn't the best approach though.
@sandfortw Thank you for suggesting that feature. I agree it makes sense to add it. I'm not sure about the `disallow` and `allow` naming, since I feel `except` would be...