[Fix] Override default Laravel method to check the type is an exact match #189
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @lindyhopchris ; hope you don't mind me giving this one ago. I've seen that there's a few issues and want to help as much as possible where I can.
I did some investigating into this one and it's because the way that the regex works within the illuminate source code and when it's split it matches due to the way that the split is done.
As we are only concerned if the header is an exact match to application/vnd.api+json then I would presume it is safe to override the method and check for an exact match disregarding the regex which is there in the illuminate source code.
I've added some tests to back up this which just check for a response with the correct header and a response with an invalid header.
Addresses #184