DeepL CORS error

  • Plugin Author Tim W

    (@timwhitlock)


    1 year, 2 months ago

    I’ve just become aware that DeepL are no longer allowing API requests directly from the browser.

    This has been policy for some time it seems, but has been working fine regardless until very recently. Perhaps they only started enforcing it.

    The next release of Loco Translate will have to proxy all their API requests via your server. Until then I think this API will be unusable from within WordPress admin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tim W

    (@timwhitlock)

    1 year, 2 months ago

    I’m now seeing the /v2/usage endpoint failing, but /v2/translate is still working. This means key validation will appear to fail, but translations may still succeed.

    The issue is the absence of the access-control-allow-origin: * header in API responses. It’s still present for the translation responses, so I’m monitoring whether this changes.

    Plugin Author Tim W

    (@timwhitlock)

    1 year, 2 months ago

    Looks like /v2/translate is disallowing CORS consistently now. Anyone experiencing this issue will have to wait for a new release, or use one of the other translation providers. I can’t give a timeline for this fix.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘DeepL CORS error’ is closed to new replies.