| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Do not join cookies with new like if they weren't before fix(middleware): ensure headers are wrapped with `Rack::Headers` Add `Rack::Headers` wrapping to middleware to prevent header manipulation issues. Added a test to verify cookies remain as an array when flagged if already in array format.
While this gem now uses lowercase headers, the Rails default configuration still defines non-lowercase headers. As a result, our Railtie will not remove those conflicting headers. This change ensures that we're accounting for both lowercase and non-lowercase default headers in Rails.
CSP3 more explicitly calls this out: > If path A consists of one character that is equal to the U+002F > SOLIDUS character (/) and path B is empty, return "Matches". A URL like `example.com/foo` will match a connect-src of `example.com`, as well as `example.com/`, so having two connect-srcs listed like this is redundant. fix: allow URIs with schema to have trailing slashes normalised Co-authored-by: Dusty Greif <dgreif@users.noreply.github.com>
Fix rake task file count output message
…s compatibility Co-authored-by: fletchto99 <718681+fletchto99@users.noreply.github.com>
Co-authored-by: fletchto99 <718681+fletchto99@users.noreply.github.com>
Co-authored-by: fletchto99 <718681+fletchto99@users.noreply.github.com>
Co-authored-by: fletchto99 <718681+fletchto99@users.noreply.github.com>
|
I don't believe this approach will solve the general case, although it may fix cases where an implementer can explicitly call a parameterized version of content_security_policy_nonce. We need to address the conflict by making sure that the nonce we provide will be used in a context where the application expects to call Rails' CSP. Alternatively there may be a mismatch in how we share the nonce value within CSP headers and how we use nonced_javascript_tag but I still need to investigate that to understand it fully. Idea: We may be able to use our initializer / activesupport hook to prepend our SecureHeaders classes ensuring that our version of of content_security_policy_nonce is called rather than Rails'. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Third-party gems (e.g., GoodJob) call content_security_policy_nonce without parameters, expecting Rails' default behavior. SecureHeaders required an explicit :script or :style parameter, causing these calls to return nil and nonces to be omitted from CSP headers.
Changes
Example
Backward compatible - existing code calling with explicit parameters unchanged.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.