Skip to content

Add support for adjusting binary detection regex in FullHttpMessageFormatter #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 29, 2021

Conversation

ostrolucky
Copy link
Contributor

@ostrolucky ostrolucky commented Aug 28, 2021

Q A
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Related tickets
Documentation
License MIT

Regrettably, in our applications, php serialize() is often used instead of JSON as a serialization format used over wire. Instead of changing default regex for everyone (which could be a security risk in case target endpoint is untrusted), this allows to inject custom regex.

Checklist

  • Updated CHANGELOG.md to describe BC breaks / deprecations | new feature | bugfix
  • Documentation pull request created (if not simply a bugfix)

…rmatter

Regrettably, in our applications, php serialize() is often used instead of JSON as a serialization format used over wire. Instead of changing ∂efault regex for everyone (which could be a security risk in case target endpoint is untrusted), this allows to inject custom regex.
@ostrolucky ostrolucky force-pushed the adjustable-binary-regex branch from 6138453 to cf70bae Compare August 28, 2021 09:41
Copy link
Contributor

@dbu dbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, good pull request! i appreciate the explanation why you need this.

and good luck when you upgrade php versions - afaik php serialization is not BC between php versions...

@dbu dbu merged commit 9da9223 into php-http:master Aug 29, 2021
@dbu
Copy link
Contributor

dbu commented Aug 29, 2021

https://github.com/php-http/message/releases/tag/1.12.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants