Default allowed REST API namespaces

  • Nazar Hotsa

    (@bugnumber9)


    5 years, 9 months ago

    Hi Gioni,

    Small request here 🙂
    You have ‘oembed’ added automatically to the list for obvious reason.
    Can you also add ‘litespeed’ by default? It’ll save some trouble for those users using LiteSpeed servers and their official plugin.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author gioni

    (@gioni)

    5 years, 9 months ago

    Hi!

    Well, the litespeed namespace is not a native part of WP, while oembed is.
    Could you give me a link to that plugin?

    Thread Starter Nazar Hotsa

    (@bugnumber9)

    5 years, 9 months ago

    Here it is: https://wordpress.org/plugins/litespeed-cache/

    On LiteSpeed-powered servers, it’ll get pre-installed via Softaculous in many popular configurations. Besides that, most people are using that plugin if the web host offers LiteSpeed.

    By default, WP Cerber will block requests made by the plugin, which isn’t a problem if you know where to check and what to do 🙂 Yet I believe it’s a great and trustworthy plugin and its functionality shouldn’t be blocked by default.
    The particular function that gets blocked by default is obtaining a domain key that’s required by some features (e.g. image optimization).

    Plugin Author gioni

    (@gioni)

    5 years, 9 months ago

    Thanks! There will be a serious update to the way how WP Cerber handles REST API restrictions soon. It will help identify possible issues with any plugin/theme that utilizes REST API. I expect it will include an admin notification in some form once such a plugin/theme gets activated. Also, do not forget that all website admins have unrestricted access to REST API by default.

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

The topic ‘Default allowed REST API namespaces’ is closed to new replies.