Error 400 bad request

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

    (@shift8)

    1 year, 1 month ago

    That happens when you try to load the CDN url without a path to a static asset.

    The CDN works by replacing all of your static asset urls (images, css, html, media) with the CDN URL above + the path to the asset.

    The CDN urls use geographic DNS resolution to resolve to an endpoint that is physically closest to the person who is requesting it.

    Regarding the unknown error you saw, this is usually the result of not putting your origin URL in the CDN dashboard exactly how it is in your browser when first loading the site. Most common reason is a “/” at the end of the url or something very simple and subtle like that.

    Thread Starter John

    (@dsl225)

    1 year, 1 month ago

    Very simple if instructions were clear.
    Managed to get rid of the “unknown” error, images were loading form the CDN but not the CSS and all other theme files managed by a cache plugin. I added the address there, at cache plugin settings, also but still not getting a fully loading page.

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

The topic ‘Error 400 bad request’ is closed to new replies.