{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifh7ndk6s6l4lvwqnh3cqcrc7fbsroxc55uieer7rlct2zh7ttkq4",
    "uri": "at://did:plc:qfsyszxhq5agxsg2n5zo4lno/app.bsky.feed.post/3mm3ftofs3hn2"
  },
  "path": "/t/400-bad-request-custom-error-page-issue/118554#post_6",
  "publishedAt": "2026-05-17T21:08:50.000Z",
  "site": "https://forum.infinityfree.com",
  "textContent": "OK, I see the issue now. The forum “fixes” the URL by encoding the percent sign, because otherwise the URL is invalid.\n\nYour custom 400 page is indeed not working, but I don’t think that’s something we can fix. Our hosting uses two web servers: OpenResty at the outer layer doing most of the work, and Apache behind it to run PHP and process .htaccess rules.\n\nWhen you send an invalid URL like `/%`, the server literally cannot parse the request. OpenResty rejects it at the outer layer because it can’t make sense of it, so the request never reaches Apache and your .htaccess rules never get applied. There’s a limit to how much control we can give you over requests that fundamentally can’t be processed.\n\nHonestly, I’m not sure there’s a practical way to trigger a 400 that would reach Apache and show your custom page. A lot of the initial validation and checking is done by OpenResty and never reaches Apache.",
  "title": "400 Bad Request custom error page issue"
}