http-proxy

Task

Currently, We use the AES algorithm to encrypt the password and provide the password back to the front end. I think It's not safe.

I suggest the following optimization:

1. The API does not return the password field. See `org.apache.shenyu.admin.controller.DashboardUse

See release notes for Envoy 1.20.0: https://www.envoyproxy.io/docs/envoy/v1.20.0/version_history/current

http: the HeaderMatcher fields exact_match, safe_regex_match, prefix_match, suffix_match and contains_match are deprecated by string_match.

The wrinkle here is that string_match was added in Envoy 1.20.0 and does not exist in 1.19.x so we cannot use this field as soon as we

Describe the bug

DOES NOT WORK

proxy.Proxy(plugins=["...", "...",]) will not result in discovering custom flags defined in the external plugins.

FOLLOWING 2 SCENARIO WORKS

proxy.Plugin(*("--plugin", "...", "--plugin", "..."))

or

proxy --plugin ....

FIX

args.plugins must be resolved prior to calling Flags.parse for custom flag discovery.