Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
2.4 GA
-
8
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
+
-
3scale 2019-03-11, 3scale 2019-05-06, 3scale 2019-05-20
Description
When apicast is deployed, the pod does not seem to honor no_proxy_env .
The customer thinks this is due to the use of client library api pisoni 1.24.0 , using Faraday framework in version 0.9.7, which has the bug. See links below.
So the connection goes through the proxy and is rejected connection.
Links :
https://github.com/lostisland/faraday/issues/471
https://github.com/lostisland/faraday/issues/487
https://github.com/lostisland/faraday/issues/700
Comment from Daria
Pisoni actually will accept any version higher than 0.9.1: https://github.com/3scale/pisoni/blob/v1.24.0/pisoni.gemspec#L21 It's actually Porta that locks Faraday version to 0.9.2: https://github.com/3scale/porta/blob/master/Gemfile.lock#L336 Adding System component to investigate whether Faraday can be bumped to 0.12.0.1 (0.12.0 is where the feature appeared) or higher. The latest release is 0.15.4. See https://github.com/lostisland/faraday/releases
To Reproduce
See this comment
Dev Notes
Could be related to gem version. We can't know until we understand the problem.
