Routes transform the request path, but do not invert the change in response paths. #462

Closed
cweider opened this Issue Jan 22, 2012 · 1 comment

Comments

Projects
None yet
3 participants
@cweider
Contributor

cweider commented Jan 22, 2012

For instance, with '.use('/the/path, handle)' the handler will see a request for /the/path/to/resource as /to/resource. If the handler responds with redirect to /other/resource nothing is done by the framework to transform this too /the/path/other/resource. I can see arguments either way, my question is whether or not the existing behavior is intentional.

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Jan 23, 2012

Member

that is intentional, though Express for example uses this knowledge in res.redirect(), but I wouldn't want to go poking around in res.setHeader() and changing values etc

Member

tj commented Jan 23, 2012

that is intentional, though Express for example uses this knowledge in res.redirect(), but I wouldn't want to go poking around in res.setHeader() and changing values etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment