You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the google translator for large entities with a lot of data to translate we receive an error. In the logs we can find that the google API returns a "411 Length Required" error.
This can be solved by sending the data as a JSON body, as the official Google documentation states, rather than adding it as query parameters.
From code I can see that the variables are given as query paramaters.
I was also wondering why the official php client is not used to accomplish this.
The text was updated successfully, but these errors were encountered:
Thank you for bringing up the issue, we greatly appreciate your feedback, and I wanted to provide you with an update on how we plan to address this concern.
In our next hotfix release, which we are planning for early next week, we will be implementing the official PHP client provided by Google for the Translator API. This client will ensure that data is transmitted in the appropriate format, effectively resolving the error and improving the overall reliability of our translation service.
If you have any further questions or concerns, please don't hesitate to reach out.
Thank you for your understanding and collaboration.
When using the google translator for large entities with a lot of data to translate we receive an error. In the logs we can find that the google API returns a "411 Length Required" error.
This can be solved by sending the data as a JSON body, as the official Google documentation states, rather than adding it as query parameters.
From code I can see that the variables are given as query paramaters.
I was also wondering why the official php client is not used to accomplish this.
The text was updated successfully, but these errors were encountered: