itsi-server 0.2.10 → 0.2.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1299ba07e4b4de522049dbf9df9c8948810c0b10f0a82da2f79585d66f803a51
-  data.tar.gz: 1f6d3ed4821cb0d8652a7659ea9ab6d60643901b307f7e925e818b69fbc5db2c
+  metadata.gz: fb707c4c3974d9d6898c48c24f707931d701a9d06a6f8c921f1ef0bdbf32d372
+  data.tar.gz: 9bb6bbecd4f4e292b2696a185bff4ff78af30f21f76aaca328df07b27928d9a0
 SHA512:
-  metadata.gz: ff5e1d66975a9406fb832e6a742679cc018507223078fac096776fd51324def81a022db3b1324456fa86f2b36f92ce7b79f4cce05c93567e48b25fc02a1ff25d
-  data.tar.gz: bd898dedfdfa333c5eb7e69d55883585218bcc7ed34c6318b33fd1cf9cf9d66fdb44b4fdeab7f5c87c8ebba3937574545fbc1ba1955e78227f2334fb8acbea77
+  metadata.gz: 9c37e1ecca3741c856714ce86f2e7865693de22c5add1eef2d93697c894b6d7d50b9e9bb115f637affd61565f77f922c586db4bd7975911fb78c7ac4f4266330
+  data.tar.gz: fcc796258023503fca0baadfe45e71ddd84210f51a3db5d13b143d94e89b538b15eab74b82c496ad42adaf28787627f27d967724a4fecce0cd7b41126df70bca

data/Cargo.lock

@@ -1644,7 +1644,7 @@ checksum = "4a5f13b858c8d314ee3e8f639011f7ccefe71f97f96e50151fb991f267928e2c"
 
 [[package]]
 name = "itsi-server"
-version = "0.2.10"
+version = "0.2.11"
 dependencies = [
  "argon2",
  "async-channel",

data/ext/itsi_scheduler/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "itsi-scheduler"
-version = "0.2.10"
+version = "0.2.11"
 edition = "2021"
 authors = ["Wouter Coppieters <wc@pico.net.nz>"]
 license = "MIT"

data/ext/itsi_server/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "itsi-server"
-version = "0.2.10"
+version = "0.2.11"
 edition = "2021"
 authors = ["Wouter Coppieters <wc@pico.net.nz>"]
 license = "MIT"

data/ext/itsi_server/src/lib.rs

@@ -86,6 +86,8 @@ fn init(ruby: &Ruby) -> Result<()> {
     response.define_method("<<", method!(ItsiHttpResponse::send_frame, 1))?;
     response.define_method("write", method!(ItsiHttpResponse::send_frame, 1))?;
     response.define_method("read", method!(ItsiHttpResponse::recv_frame, 0))?;
+    response.define_method("flush", method!(ItsiHttpResponse::flush, 0))?;
+    response.define_method("closed?", method!(ItsiHttpResponse::is_closed, 0))?;
     response.define_method(
         "send_and_close",
         method!(ItsiHttpResponse::send_and_close, 1),

data/ext/itsi_server/src/ruby_types/itsi_http_response.rs

@@ -272,6 +272,14 @@ impl ItsiHttpResponse {
         // not implemented
     }
 
+    pub fn flush(&self) {
+        // no-op
+    }
+
+    pub fn is_closed(&self) -> bool {
+        self.data.response_writer.write().is_none()
+    }
+
     pub fn send_and_close(&self, frame: Bytes) -> MagnusResult<()> {
         let result = self.send_frame_into(ByteFrame::End(frame), &self.data.response_writer);
         self.data.response_writer.write().take();

data/lib/itsi/http_request.rb

@@ -11,7 +11,8 @@ module Itsi
     include ResponseStatusShortcodes
     attr_accessor :hijacked
 
-    EMPTY_IO = StringIO.new("")
+    EMPTY_IO = StringIO.new("").tap { |io| io.set_encoding(Encoding::ASCII_8BIT) }
+
     RACK_HEADER_MAP = StandardHeaders::ALL.map do |header|
       rack_form = if header == "content-type"
                     "CONTENT_TYPE"
@@ -49,9 +50,7 @@ module Itsi
       "rack.version" => nil,
       "rack.url_scheme" => "",
       "rack.input" => "",
-      "rack.hijack" => "",
-      "CONTENT_TYPE" => nil,
-      "CONTENT_LENGTH" => nil
+      "rack.hijack" => ""
     }.freeze
 
     def to_rack_env
@@ -75,20 +74,20 @@ module Itsi
       env["rack.hijack"] = method(:hijack)
       headers.each do |(k, v)|
         env[case k
-          when "content-type" then "CONTENT_TYPE"
-          when "content-length" then "CONTENT_LENGTH"
-          when "accept" then "HTTP_ACCEPT"
-          when "accept-encoding" then "HTTP_ACCEPT_ENCODING"
-          when "accept-language" then "HTTP_ACCEPT_LANGUAGE"
-          when "user-agent" then "HTTP_USER_AGENT"
-          when "referer" then "HTTP_REFERER"
-          when "origin" then "HTTP_ORIGIN"
-          when "cookie" then "HTTP_COOKIE"
-          when "authorization" then "HTTP_AUTHORIZATION"
-          when "x-forwarded-for" then "HTTP_X_FORWARDED_FOR"
-          when "x-forwarded-proto" then "HTTP_X_FORWARDED_PROTO"
-          else RACK_HEADER_MAP[k]
-          end
+            when "content-type" then "CONTENT_TYPE"
+            when "content-length" then "CONTENT_LENGTH"
+            when "accept" then "HTTP_ACCEPT"
+            when "accept-encoding" then "HTTP_ACCEPT_ENCODING"
+            when "accept-language" then "HTTP_ACCEPT_LANGUAGE"
+            when "user-agent" then "HTTP_USER_AGENT"
+            when "referer" then "HTTP_REFERER"
+            when "origin" then "HTTP_ORIGIN"
+            when "cookie" then "HTTP_COOKIE"
+            when "authorization" then "HTTP_AUTHORIZATION"
+            when "x-forwarded-for" then "HTTP_X_FORWARDED_FOR"
+            when "x-forwarded-proto" then "HTTP_X_FORWARDED_PROTO"
+            else RACK_HEADER_MAP[k]
+            end
         ] = v
       end
       env
@@ -154,8 +153,8 @@ module Itsi
     def build_input_io
       case body_parts
       when nil then EMPTY_IO
-      when String then StringIO.new(body_parts)
-      when Array then File.open(body_parts.first, "rb")
+      when String then StringIO.new(body_parts).tap { |io| io.set_encoding(Encoding::ASCII_8BIT) }
+      when Array then File.open(body_parts.first, "rb").tap { |io| io.set_encoding(Encoding::ASCII_8BIT) }
       else body_parts
       end
     end

data/lib/itsi/server/config/middleware/endpoint/_index.md

@@ -5,9 +5,10 @@ prev: deny_list/
 next: controller/
 ---
 
+> If you're after running a rack app using a fully-featured framework, e.g. a Ruby on Rails or Sinatra, take a look at the [Rackup File](/middleware/rackup_file) middleware instead.
+
 The **endpoint** middleware allows you to define an ultra light-weight, inline, Ruby endpoint.
 
-> If you're after running a rack app using a fully-featured framework, e.g. a Ruby on Rails or Sinatra, take a look at the [Rackup File](/middleware/rackup_file) middleware instead.
 This feature can be useful for quickly prototyping, building small pieces of isolated functionality, or minimal endpoints where high throughput is essential.
 
 `endpoint` has several variants, that further restrict the endpoint to respond to specific HTTP methods:

data/lib/itsi/server/config/options/certificates.md

@@ -9,11 +9,11 @@ Itsi can automatically generate TLS certificates for you, both in development an
 To automatically generate a TLS certificate in development, just bind using the `https` scheme.
 E.g.
 ```ruby {filename=Itsi.rb}
-bind "https://localhost"
+bind "https://0.0.0.0"
 
 or
 
-bind "https://localhost:8443"
+bind "https://0.0.0.0:8443"
 ```
 Itsi will generate a local development CA for you if it does not yet exist, then use this to
 sign a just-in-time certificate for your server.

data/lib/itsi/server/config/options/scheduler_threads.md

@@ -3,7 +3,7 @@ title: Scheduler Threads
 url: /options/scheduler_threads
 ---
 
-You can explicitly spawn a pool of non-blocking scheduler threads and divide work across traditional blocking and non-blocking threads, using [location](/middleware/location) blocks.
+You can explicitly spawn a pool of non-blocking scheduler threads and divide work across traditional/blocking and non-blocking threads, using [location](/middleware/location) blocks.
 
 This allows you to safely dip your toes into using non-blocking threads for specific I/O heavy operations without having to port an entire application to non-blocking I/O.
 

data/lib/itsi/server/default_config/Itsi.rb

@@ -31,8 +31,8 @@ fiber_scheduler nil
 
 # If you bind to https, without specifying a certificate, Itsi will use a self-signed certificate.
 # The self-signed certificate will use a CA generated for your host and stored inside `ITSI_LOCAL_CA_DIR` (Defaults to ~/.itsi)
-# bind "https://localhost:3000"
-# bind "https://localhost:3000?domains=dev.itsi.fyi"
+# bind "https://0.0.0.0:3000"
+# bind "https://0.0.0.0:3000?domains=dev.itsi.fyi"
 #
 # If you want to use let's encrypt to generate you a real certificate you and pass cert=acme and an acme_email address to generate one.
 # bind "https://itsi.fyi?cert=acme&acme_email=admin@itsi.fyi"

data/lib/itsi/server/rack/handler/itsi.rb

@@ -8,10 +8,11 @@ module Rack
         port = options.fetch(:Port, 3001)
         ::Itsi::Server.start(
           {
-            app: app,
             binds: ["http://#{host}:#{port}"]
           }
-        )
+        ) do
+          run app
+        end
       end
     end
   end

data/lib/itsi/server/version.rb

@@ -2,6 +2,6 @@
 
 module Itsi
   class Server
-    VERSION = "0.2.10"
+    VERSION = "0.2.11"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: itsi-server
 version: !ruby/object:Gem::Version
-  version: 0.2.10
+  version: 0.2.11
 platform: ruby
 authors:
 - Wouter Coppieters
@@ -91,7 +91,6 @@ files:
 - ".rubocop.yml"
 - Cargo.lock
 - Cargo.toml
-- README.md
 - Rakefile
 - exe/itsi
 - ext/itsi_acme/Cargo.toml

data/README.md

@@ -1,49 +0,0 @@
----
-type: docs
-sidebar:
-  exclude: true
----
-
-# ItsiServer
-
-TODO: Delete this and the text below, and describe your gem
-
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/itsi_server`. To experiment with that code, run `bin/console` for an interactive prompt.
-
-## Installation
-
-TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
-
-Install the gem and add to the application's Gemfile by executing:
-
-```bash
-bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
-```
-
-If bundler is not being used to manage dependencies, install the gem by executing:
-
-```bash
-gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
-```
-
-## Usage
-
-TODO: Write usage instructions here
-
-## Development
-
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
-
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/itsi_server. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/itsi_server/blob/master/CODE_OF_CONDUCT.md).
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
-
-## Code of Conduct
-
-Everyone interacting in the ItsiServer project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/itsi_server/blob/master/CODE_OF_CONDUCT.md).