Skip to content

Commit

Permalink
docs: update references to 4.2.1 to read 4.3.0 instead
Browse files Browse the repository at this point in the history
Signed-off-by: Matthew Weier O'Phinney <matthew@weierophinney.net>
  • Loading branch information
weierophinney committed Jul 25, 2022
1 parent 8b625b4 commit 0c049ba
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions docs/book/v4/cookbook/provide-a-request-id.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,9 +68,9 @@ This approach:

## Alternate solution

INFO: Available since 4.2.1
INFO: Available since 4.3.0

As of mezzio-swoole 4.2.1, you can now define and consume a `Laminas\Diactoros\ServerRequestFilter\FilterServerRequestInterface` service to modify the `ServerRequestInterface` generated when a request arrives.
As of mezzio-swoole 4.3.0, you can now define and consume a `Laminas\Diactoros\ServerRequestFilter\FilterServerRequestInterface` service to modify the `ServerRequestInterface` generated when a request arrives.
This can be done in one of two ways, depending on whether or not you explicitly define the `FilterServerRequestInterface` service.

### Without a defined FilterServerRequestInterface
Expand Down
6 changes: 3 additions & 3 deletions docs/book/v4/migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,11 @@ To change behavior of the class, we recommend using its [event system](events.md

## ServerRequestSwooleFactory

INFO: Since 4.2.1
INFO: Since 4.3.0

Starting in version 4.2.1, the behavior of `Mezzio\Swoole\ServerRequestSwooleFactory` changes slightly with regards to how it handles the various `X-Forwarded-*` headers.
Starting in version 4.3.0, the behavior of `Mezzio\Swoole\ServerRequestSwooleFactory` changes slightly with regards to how it handles the various `X-Forwarded-*` headers.
These headers are conventionally used when a server is behind a load balancer or reverse proxy in order to present to the application the URL that initiated a request.
Starting in version 4.2.1, by default, these headers are only honored if the request received originates from a reserved subnet (e.g., localhost; class A, B, and C subnets; IPv6 private and local-link subnets).
Starting in version 4.3.0, by default, these headers are only honored if the request received originates from a reserved subnet (e.g., localhost; class A, B, and C subnets; IPv6 private and local-link subnets).

If you want to honor these headers from any source, or if you never want to allow them, you can provide an alternate implementation via the `Laminas\Diactoros\ServerRequestFilter\FilterServerRequestInterface` service.
As an example, you could use the following to dis-allow them:
Expand Down

0 comments on commit 0c049ba

Please sign in to comment.