Repository navigation
StateFrame 0.4.37
StateFrame 0.4.37: proxy credentials never reach the endpoint.
Changes
- Security: direct requests now remove a caller-supplied
Proxy-Authorizationheader before sending, so a proxy-only credential cannot be forwarded to your endpoint. - Security: when a request goes through a proxy, the proxy credentials stay with the proxy and are not sent again after a redirect to a different origin.
- How requests are routed is unchanged: StateFrame still connects to your endpoint directly and does not use environment proxy settings.
Known issues (fixes planned)
- In-place runs and exported patches can change the line endings or byte-order mark of untouched text files in the edit scope (see KNOWN_LIMITATIONS). A fix is being tested now.
- Linux: checks that run Go or Node programs fail under StateFrame's check memory limit. macOS is not affected.
- The first request of a run can differ between runs in one optional orientation section, depending on local cache state.
- On endpoints without an exact tokenizer, very dense content can be underestimated and push a request past the context limit.