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
Intermittent 501 Not Implemented Error Due to Unexpected 'offsetGet' Method in Guzzle Requests #3179
Comments
But the log further below shows this:
This is your code calling this? What happens at and around like 36 of |
@mfn About your question
I see this line |
Well, first thing coming to my mind is https://www.php.net/manual/en/arrayaccess.offsetget.php . Guzzle isn't using that so… |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 2 weeks if no further activity occurs. Thank you for your contributions. |
Guzzle version(s) affected: 6.3.3
PHP version: 7.2.34
cURL version: 7.74.0
Description
I'm encountering an issue with Guzzle where it appears to be attempting to make an HTTP request using the offsetGet method, which is not a standard HTTP method. This results in a 501 Not Implemented response from the server. The issue occurs intermittently on specific ECS instances, and all instances are running the same source code.
How to reproduce
The issue is intermittent and doesn't occur consistently, but here's a rough outline of how it can be observed:
Set up an environment with multiple ECS instances running the same source code and Guzzle configuration.
Occasionally, on one of the ECS instances, when making an HTTP request using Guzzle, the request may be incorrectly using the offsetGet method instead of a valid HTTP method.
This incorrect request results in a 501 Not Implemented response from the server is trigger from this code
Possible Solution
I don't have a specific solution at this time, as the issue is intermittent and doesn't seem to be directly related to the source code or Guzzle configuration. It may require further investigation to identify the root cause.
Additional context
Log bellow:
I have done some research on the internet and found a link related to the topic.
https://stackoverflow.com/questions/66710501/guzzlehttp-sending-weird-request-with-weird-http-method
The temporary solution is to reset the container, in accordance with the current situation. But it will continue in the future.
The text was updated successfully, but these errors were encountered: