PHPAML

Documentation · Chapter 19

Trace a request from URL to response.

For a Web failure, follow the chain: browser, port, public entry point, router, middleware, controller, service, persistence, response.

Every lesson starts from the problem, explains the mechanism, then gives a concrete verification.

LESSON OBJECTIVE

What you will be able to do

Trace Web failures through connection, public entry, routing, middleware, application code, persistence, and response.

Connection refused versus HTTP error

Connection refused means no process listens at that host/port. A 404, 403, or 500 means the server answered and narrows the investigation.

phpaml — zsh
aml serve 127.0.0.1:8910
aml routes
curl -i http://127.0.0.1:8910/missing

Route and controller failures

aml routes proves registration. Then verify HTTP method, path parameters, controller class, action visibility, namespace, and autoloading.

Headers and public root

Serve public as the document root. Inspect CSP, cache, MIME type, and exact filename casing when CSS, scripts, or images fail.

CHECKPOINT

Before you continue

Does the status mean no server answered, the route is absent, access is forbidden, or application execution failed?