-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
How do I use the Rack handler? #6
Comments
Hmm |
Isn't Transfer-Encoding a response header? |
Here's what I'm seeing with net-http-server 0.2.1 and rack 1.4.1: run lambda { |env| [200, {'Content-Type' => 'text/html'}, ['hello world']] }
|
Ah it appears Rack is doing it's own Chunked Encoding: T 127.0.0.1:49996 -> 127.0.0.1:9292 [AP] GET / HTTP/1.1..Accept: */*..User-Agent: Ruby..Host: localhost:9292.... ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] HTTP/1.1 200 OK.. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] Content-Type: text/html.. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] Transfer-Encoding: chunked.. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] .. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] 10.. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] b..hello world.. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] .. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] 5.. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] 0.... ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] .. ## T 127.0.0.1:9292 -> 127.0.0.1:49996 [AP] 0.... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rackup -s HTTP
doesn't work (I think rack is trying to loadrack/handler/hTTP.rb
), neither doesrackup -s http
, as you don't callregister
in the handler.The text was updated successfully, but these errors were encountered: