Alexey Zapparov

I'm going to work on (have some preliminray code that is not ready to be shared yet) with session alike object (I'm still sketching out API), but the very simple...

@sj26, I agree that we should avoid introducing new *"standard"* and follow RFC, which I believe `Addressable::URI#join` is following. --- 

@paul I must admit I'm also surprised everytime, but, I guess it's better to follow RFC as was mentioned above.

Agree. Although I also find `URI.join` a bit weird, especially when comparing it to `File.join`, but as we are handling URIs here we should follow RFC of URI joining. After...

I believe we should use `#last` value of content-length headers.

Yeah. Would be nice to know which is default behaviour other clients use. I see there are 3 ways on how to act in given scenario: 1. consider first value...

I've wrote a small testing server: ``` ruby # frozen_string_literal: true require "socket" server = TCPServer.new(3000) loop do Thread.new(server.accept) do |io| status = 200 headers = [] case io.gets[%r{^GET /(\d+)...

Personally I prefer failing in case if multiple different content length values are given: ``` ruby def content_length values = headers.get("Content-Length").uniq raise "WTF? o_O" if 1 < values.size values.first&.to_i end...

Worth to test how they handle absolutely undxpected value of content length as well.

Enhanced dummy server with couple of more scenarios: ``` ruby # frozen_string_literal: true require "socket" server = TCPServer.new(3000) loop do Thread.new(server.accept) do |io| status = 200 headers = [] case...