[BUG] Only Java level Web proxy settings apply about rest-list-parameter-plugin HOT 3 CLOSED

Hi @jamesnswithers!

Thank you for the comment, and yes this is common to have your proxy to just allow access to the outside world.
However, then there is the field "no proxy" that allows for wildcard definitions.
Say you have your local services like the following:

• gitea.local.lan
• nexus.local.lan
• service.local.lan

then you can add this to the no proxy field and none of those addresses would get sent to the proxy:

• *.local.lan

NOTE: I would be not alone to "solve" this issue this way, it is common practice among plugins, just that I have overlooked this in my initial implementation xD

(but let me know if that still affects your use-case, then i can add a global config to disable this behavior 😉 )

from rest-list-parameter-plugin.

I already know how to fix this thanks to the github-plugin using the same HTTP library and them already supporting this (see here, and here).

I will most likely wait with a fix for this till 1.2.0, since I am already touching the OKHttp (the HTTP library used) connection and client there and can incorporate this fix with it.

Should someone however face this BUG and need a immediate fix, then let me know or set the global Java HTTP proxy properties for now.

from rest-list-parameter-plugin.

For our use case fixing this 'bug' would hurt us as we set the Plugin Manager proxy so we can reach out to the internet for plugin updates however all of the webservices we fetch data from are internal which are not available through our corporate proxy. Food for thought as i'm not sure how common place this.

from rest-list-parameter-plugin.