Releases: configcat/configcat-proxy
Releases · configcat/configcat-proxy
v0.2.2
v0.2.1
Added
-
Option to define regex patterns for CORS allowed origins.
http: api: cors: enabled: true allowed_origins_regex: patterns: - .*\.example1\.com - .*\.example2\.com if_no_match: https://example1.com
The
if_no_match
field is mandatory when the regex option is set because that value is used in theAccess-Control-Allow-Origin
header when an incoming request's origin doesn't match with any configured patterns.If both
allowed_origins_regex
andallowed_origins
options are set, the list inallowed_origins
will be checked first and if there isn't a match, the execution will jump to evaluate the regex patterns.
v0.2.0
Added
- The ability to set allowed origins for CORS.
When the allowed origins is set, the Proxy will include only that origin in theAccess-Control-Allow-Origin
response header, which matches the request'sOrigin
. When there's no matching request origin, the Proxy will set theAccess-Control-Allow-Origin
response header to the first item in the allowed origins list.
Breaking Changes
- The CORS configuration option for API, CDN Proxy, and SSE has been changed:
- Old:
http: api: allow_cors: true
- New:
http: api: cors: enabled: true allowed_origins: - https://example1.com - https://example2.com
- Old:
v0.1.6
Added
- Ability to load
options.yml
from a default location.
The default location varies by platform:- Windows:
%PROGRAMDATA%\configcat\proxy\options.yml
, usuallyC:\ProgramData\configcat\proxy\options.yml
- macOS:
/Library/Application Support/configcat/proxy/options.yml
- Linux:
/etc/configcat/proxy/options.yml
- Windows: