Rapid Translate Multi Traduction
よって
oussama sibari |
更新済み hace 13 días |
Text Analysis
人気
9.8 / 10
レイテンシー
342ms
サービスレベル
100%
Health Check
N/A
すべてのディスカッションに戻る
411 errors
CyberscapeMedia
2년 전
Hello,
We are getting 411 errors for some input html text.
Note sure if it helps, but we noticed in the error response bodies the phrase “That’s all we know.” So it looks like this error response is coming from your translation API provider without being modified by your own API.
Having looked into it, we think that you might be missing a “Content-Length” header in the calls you make to your translation API provider, so this could be a possible fix.
Could you please look into this?
Thanks!
ディスカッションに参加しましょう－以下にコメントを追加してください：
ログイン/サインアップして新しいコメントを投稿
Hi there! Thank you for contacting Us, I apologize for replying late.
In response to your questions: We inform you that the max length is 8500 character.
I appreciate your patience. If you have any follow-up questions or concerns, I’m here to help!
I have the same problem
Following up on this, yet again! Can you please look into this??? Thanks!
Plz, look at this issue. We are receiving 70% of 411 errors.
Hello again,
Just following up on this again. Any chance of a fix???
Thanks!
Hello,
Any chance you can get back to me on this?
Here is some sample input html taken from Wikipedia that generates a 411 error on your API…
https://rentry.co/ov4c7
This is just one example of many. It seems to be nothing to do with the length, as many longer html snippets work OK.
This generates the following error output from your API…
"Error 411 (Length Required)!!1
POST requests require a Content-length header. That’s all we know."
Looks like you need to provide a Content-length header to your underlying translation provider(?)
Could you please look into this? Thank you!