Replies: 4 comments
-
Hmm |
Beta Was this translation helpful? Give feedback.
0 replies
-
Isn't Transfer-Encoding a response header? |
Beta Was this translation helpful? Give feedback.
0 replies
-
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']] }
|
Beta Was this translation helpful? Give feedback.
0 replies
-
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.... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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.Beta Was this translation helpful? Give feedback.
All reactions