Bump guzzlehttp/psr7 from 1.4.2 to 1.9.1
Bumps guzzlehttp/psr7 from 1.4.2 to 1.9.1.
Release notes
Sourced from guzzlehttp/psr7's releases.
1.9.1
See change log for changes.
1.9.0
See change log for changes.
1.8.5
See change log for changes.
1.8.4
See change log for changes.
1.8.3
See change log for changes.
1.8.2
See change log for changes.
1.8.1
See change log for changes.
1.8.0
See change log for changes.
1.7.0
See change log for changes.
Revert PSR-7 type assertions
1.6.0 introduced a few type assertions to enforce types defined by PSR-7. Unfortunately that break the library for users not strictly following the PSR-7 standard. Since the users impacted by this change seems to be rather large, this hotfix reverts that change with the note that we will reapply it in 2.0.0, so fixing this is recommended regardless of which version you use.
1.6.0
Version 1.6.0 is released which will likely be the last minor release in 1.x. We're focussing 2.0 now with support for psr/http-factory, PHP 7.2 requirement and type declarations.
Added
- Allowed version
^3.0ofralouphie/getallheadersdependency (#244)- Added MIME type for WEBP image format (#246)
- Added more validation of values according to PSR-7 and RFC standards, e.g. status code range (#250, #272)
Changed
- Tests don't pass with HHVM 4.0, so HHVM support got dropped. Other libraries like composer have done the same. (#262)
- Accept port number 0 to be valid (#270)
Fixed
... (truncated)
Changelog
Sourced from guzzlehttp/psr7's changelog.
1.9.1 - 2023-04-17
Fixed
- Fixed header validation issue
1.9.0 - 2022-06-20
Added
- Added
UriComparator::isCrossOriginmethod1.8.5 - 2022-03-20
Fixed
- Correct header value validation
1.8.4 - 2022-03-20
Fixed
- Validate header values properly
1.8.3 - 2021-10-05
Fixed
- Return
nullin caching stream size if remote size isnull1.8.2 - 2021-04-26
Fixed
- Handle possibly unset
urlinstream_get_meta_data1.8.1 - 2021-03-21
Fixed
- Issue parsing IPv6 URLs
- Issue modifying ServerRequest lost all its attributes
1.8.0 - 2021-03-21
Added
- Locale independent URL parsing
- Most classes got a
@finalannotation to prepare for 2.0
... (truncated)
Commits
e4490caRelease 1.9.1c8b21deRelease 1.9.118fd891Patch header validation issue0e75375Remove branch alias7cd3009Update CI workflows (#552)e98e3e6Release 1.9.0 (#520)337e3adRelease 1.8.5 (#491)902db15Release 1.8.4 (#486)1afdd86Release 1.8.3 (#446)a0c4a5fReturn null in caching stream size if remote is null (#438)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
Dear @VeronikaKusova, Thank you for you clear description about the issue. We are currently analyzing the problem and we will come back to you as soon as possible. Regards
Dear @danielnavarrogeo, thank you for your responce. I have continued to investigate this issue. I have tried to test it on a different service, that runs on a different map portal (so I can change its responces more easily). If I test this service and if there isn't any comment on the first position in the GetFeature response, it passes the whole Initialization and basic checks test module. But if I add a comment in the GetFeature response (on the first position), the test fails the same way as I have reported before (in the same test step with the same error messages etc.).
I can't send you a link to this "testing" service, because it is not open to public. But I hope this information will help you anyway.
Regards. Veronika
Dear @VeronikaKusova,
Please, in order to reproduce the error on our environment, would you mind to provide us with the data by email sending them to [email protected]. All data sent to this address will be completely confidential and will only be used in order to improve the validator. Once the issue has been solved all data will be deleted.
Thank you and best regards.
@josemasensio, do you mean/want service endpoint of my testing service? But at the moment there is a comment on the position of the first child in the GetFeature response, so the test fails the same way as this service: http://services.cuzk.cz/wfs/inspire-AU-wfs.asp?service=WFS&request=getCapabilities Or do you want me to delete the comment in the testing service and send you the link? Or do you need anything else?
Dear @VeronikaKusova,
I can't send you a link to this "testing" service, because it is not open to public. But I hope this information will help you anyway.
I was refering to this service, apologise if my requirement was not clear.
Best regards.
Dear @VeronikaKusova
We are working on this issue. We will come back to you when a solution is implemented.
Regards
Dear @VeronikaKusova,
We noticed that the service has changed. Please, could you provide us with the service again? If you prefer, you can provide us the service as a file and we will deploy this on our local environment.
Thank you and best regards.
Dear @josemasensio, I am sorry for those changes, but we wanted to move forward in testing.
We provide some other services with the same issue and the changes haven’t been done there, yet. (All these services run on the same map server). Access points to these services: http://services.cuzk.cz/wfs/inspire-CP-wfs.asp?service=WFS&request=getCapabilities http://services.cuzk.cz/wfs/inspire-BU-wfs.asp?service=WFS&request=getCapabilities
Can you use them instead of the original service? I run the ETS for Pre-defined WFS in Soap-UI and it seems these two services have the exact issues as the original one. So, I hope you can use them instead.
I apologize for the inconvenience. Best regards.