19Nis
Can we identify secondary contexts from web application error messages? [closed]
If a web app is giving normal "not found" page for /blablablaalsdf but for certain paths, it doesn't give the normal 404 page but gives Cannot Get /<path> instead, would this be an indicator that this path (and whatever under it) is being proxied to another host?
If not, what could make it return the generic express error for these specific pages?
