What's Changed
- The incompatible updates of the restful api not mentioned in the previous version of the changelog have been rolled back, solving the problem that the related gui cannot refresh the configuration
- Note that for security reasons, we are currently planning to restrict the "path" parameter of
/configsin restful api in the next version, and its directory also needs to be inSAFE_PATHSor workdir. It is recommended that downstream clients adapt to this change in advance. (This change has been applied to alpha version 2116640) - Other incompatible updates are the same as v1.19.6:
- For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the
SAFE_PATHSenvironment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)- In addition, support for specifying
routing-markandinterface-nameforproxy-groupshas been removed. Please specify the relevant parameters inproxiesdirectly.
BUG & Fix
Maintenance
- 00cceba docs: update config.yaml follow 7e7016b (#2022) by @muink
- a4fcd3a chore: rollback incompatible changes to updateConfigs api by @wwqgtxx
Full Changelog: v1.19.6...v1.19.7