Open ryanerwin opened 4 years ago
Hello @ryanerwin ,
But if you copy and paste the 404 URL directly in the browser you have a 200 response.
Looks like Google is blocking the requests if don't come from his domain. I need to investigate this.
Thanks for reporting.
Interestingly enough, in my case, only the new link works to get a 200...
Even pasting the old link into a new window, I'm getting a 403
(forbidden)
I see, but the extension don't use the old link, the actual URI generated to use the TTS option is
You can find it here:
https://github.com/itsecurityco/to-google-translate/blob/master/src/config.js#L31
I see, but the extension don't use the old link, the actual URI generated to use the TTS option is
That's odd... Doesn't seem like it should be possible to ever get the old link to pop up, because as you pointed out, that link isn't even in the code...
Is the TTS function working for you?
Unfortunately, I still can't get it to work. Yet using ImTranslator (way too much bloat for me) the TTS option does work.
Any other suggestions on how to get to the bottom of this?
to-google-translate seems to be using an older, no longer accessible version of a call to the Google Translate TTS engine.
When using Right Click > to Google Translate > Listen...
Or the keyboard shortcut CTRL + ALT + 2...
I keep on getting the following popup, and when I inspect the details, it seems Firefox is getting a 404 on the TTS audio file...
Example of current link with 404:
I believe the old link was basically:
And the new link is basically: