Closed joaotavora closed 6 years ago
Thanks, that works fine. Will you add it in snooze ?
Will you add it in snooze ?
No because the particular details of redirection are the web server's responsibility, and snooze is an URL router. This one works for hunchentoot but will possibly fail for clack or wookie or whatever.
Of course I won't mind if a separate project, say snooze-utils
is created that addresses this and creates multiple versions of these utils (one for each server) and dispatches appropriately given the web server in use.
makes sense, but a bit of a shame, since a redirection mechanism is always used alongside routing.
This one works for hunchentoot but will possibly fail for clack or wookie or whatever.
Clack is supposed to be server agnostic, it uses Hunchentoot by default and can be told to use Woo or others. So require
ing Clack and building the function on it would be an all-in-one solution. Can't judge more though, will have to try.
ps: I'll add some information in the wiki.
@vindarel asks in #5:
It's a question of signalling a 303 with an appropriate
Location:
header value. I setup a helper function calledredirect-to
or something like that. This one is for hunchentoot but i suppose it's easy to write one for clack or anything else you use...and then in some route, say
authenticate