-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different route behavior when using different backends #3
Comments
Code seems OK. Previously, I've used weblocks with Which ql dists versions do you have? What will output this command:
|
|
I have tried something like this:
and still, the same error |
BTW, a simple bug is at here .
is a choice |
It seems that path-info could be |
For woo, it returns NIL as path-info when visit '/', so you need to treat it cautiously.
|
As for wookie, you just simply won't get "/" when visit "/" I think it is related to clack more than weblocks |
Most probably, the problem is in Lack Request: https://github.com/fukamachi/lack/blob/master/src/request.lisp#L67-L116 |
Yes it is possible too.
and the same error occur again. For woo:
gives:
when visiting '/' |
Alright, I found it that both woo and wookie is using quri, which return NIL when visit something like 127.0.0.1:8080. I have open an issue here, should fix them both. |
Example
when using :
(weblocks/server:start :port 40000 :server-type :hunchentoot :interface "127.0.0.1")
, you should get "Test" from 127.0.0.1:4000But both
(weblocks/server:start :port 40000 :server-type :wookie :interface "127.0.0.1")
and(weblocks/server:start :port 40000 :server-type :woo :interface "127.0.0.1")
give error like this:Where am I wrong?
The text was updated successfully, but these errors were encountered: