Does lack of loopback really affect block editor?

  • AndyHenderson

    (@andyhenderson)


    7 years, 1 month ago

    Our ISP has disabled loopback requests. I’ve tried to get this fixed – and I’m now trying again using the ‘Site Health’ page as ammunition. In the meantime we are getting by with ALTERNATE_WP_CRON.

    In addition to ‘Your site could not complete a loopback request’ we also see a critical issue: ‘The REST API encountered an error’. I think that also relates to the loopback issue because the reported error is the same: “cURL error 56: Failure when receiving data from the peer”.

    The additional information says “One example is the block editor screen, which relies on this to display, and save, your posts and pages”. From my limited understanding the block editor makes its requests from JavaScript in which case they aren’t loopback requests because they come from the browser, not the server. Is that right?

    Andy

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

    (@joyously)

    7 years, 1 month ago

    It sounds like two messages were condensed to one.
    Loopback is used in the code editor to make sure no fatal errors were introduced by the code edit.
    The block editor uses the REST API for all of its communication to the server, but some blocks are server-side-rendered, which could in some cases be a loopback (?), not sure.
    But you can disable the REST API for external requests and still use the block editor, because it’s all internal requests.

    We were just a few minutes ago discussing a ticket which wanted to use the loopback to test that a plugin or theme was okay to install before actually installing it.
    https://core.trac.ww.wp.xz.cn/ticket/37301

    Thread Starter AndyHenderson

    (@andyhenderson)

    7 years, 1 month ago

    Thanks for getting back.

    >>>But you can disable the REST API for external requests and still use the block editor, because it’s all internal requests.<<<

    I guess that’s my concern. Lack of loopback does not prevent external requests (e.g. from JavaScript running in a browser) but it does prevent requests from our server back to the same server.

    If the block editor (or any other service) relies on loopback requests, that’s a big deal because there are many ISPs (including ours) that see preventing it as non-negotiable.

    Andy

    richardshort

    (@richardshort)

    6 years, 10 months ago

    My ISP does not allow loopback.

    Today I upgraded from 4.9 to 5.2.2 and have spent all day talking to ISP support as I had CRON problems and Site Health showing a critical error with REST API about “cURL error 56: Failure when receiving data from the peer”.

    I have not got anywhere with them, then I found this post. The ALTERNATE_WP_CRON seems to have fixed the CRON problems.

    How do I disable the REST API to external requests, and, more importantly will this impact anything ? Or do I just live with this error message for REST API, as Site Health is forever going to warn me that my site can’t complete a loopback request!

    Thanks

    Richard

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

The topic ‘Does lack of loopback really affect block editor?’ is closed to new replies.