This is exactly my thinking too and why the request in my example MVC is passed on to the view, controller and model. The information needed to get all jobs done is in the request. However, the request is just the returned/ modified answer from the previous response, which was formed by the model. The view (the actual response) is only a representation of the model, be it HTML, JSON, PDF, etc. When you talk in “page controller terms”, you simply can’t say that really. The response in web MVC is a mixed representation of model and in some cases, too much controller logic (the dreaded fat controller). In other words, having to figure out what representation/ response needs to be sent in the controller with which model means a single controller class automatically breaks SRP. It is also why controllers in web MVC in the popular frameworks are rarely portable and hard to test.
Scott