sailorproject/sailor

404 on Xavante

Open

#24 opened on Nov 6, 2014

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Lua (868 stars) (123 forks)batch import
bughelp wanted

Description

When there are no 404 custom page configured, Xavante fails to exhibit the 404 default page even though we are returning 404 to the server.

Contributor guide

Tech stack
lua
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic LuaFamiliarity with Sailor MVC structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine how Sailor handles HTTP responses when no custom 404 page is configured. Check the default error rendering in the framework's core (likely in 'sailor/lib/' or similar) and the integration with Xavante to determine why the default 404 page is not displayed despite returning a 404 status. Look at any existing tests or documentation on error customization.