rfuzz 0.6 → 0.7

data/examples/mongrel_test_suite/test/http/caching_in_http.rb

@@ -0,0 +1,140 @@
+require 'rfuzz/session'
+
+context "13: Caching in HTTP" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "13.1.1: Cache Correctness" do
+  end
+
+
+  specify "13.1.2: Warnings" do
+  end
+
+
+  specify "13.1.3: Cache-control Mechanisms" do
+  end
+
+
+  specify "13.1.4: Explicit User Agent Warnings" do
+  end
+
+
+  specify "13.1.5: Exceptions to the Rules and Warnings" do
+  end
+
+
+  specify "13.1.6: Client-controlled Behavior" do
+  end
+
+
+  specify "13.2: Expiration Model" do
+  end
+
+
+  specify "13.2.1: Server-Specified Expiration" do
+  end
+
+
+  specify "13.2.2: Heuristic Expiration" do
+  end
+
+
+  specify "13.2.3: Age Calculations" do
+  end
+
+
+  specify "13.2.4: Expiration Calculations" do
+  end
+
+
+  specify "13.2.5: Disambiguating Expiration Values" do
+  end
+
+
+  specify "13.2.6: Disambiguating Multiple Responses" do
+  end
+
+
+  specify "13.3: Validation Model" do
+  end
+
+
+  specify "13.3.1: Last-Modified Dates" do
+  end
+
+
+  specify "13.3.2: Entity Tag Cache Validators" do
+  end
+
+
+  specify "13.3.3: Weak and Strong Validators" do
+  end
+
+
+  specify "13.3.4: Rules for When to Use Entity Tags and Last-Modified Dates" do
+  end
+
+
+  specify "13.3.5: Non-validating Conditionals" do
+  end
+
+
+  specify "13.4: Response Cacheability" do
+  end
+
+
+  specify "13.5: Constructing Responses From Caches" do
+  end
+
+
+  specify "13.5.1: End-to-end and Hop-by-hop Headers" do
+  end
+
+
+  specify "13.5.2: Non-modifiable Headers" do
+  end
+
+
+  specify "13.5.3: Combining Headers" do
+  end
+
+
+  specify "13.5.4: Combining Byte Ranges" do
+  end
+
+
+  specify "13.6: Caching Negotiated Responses" do
+  end
+
+
+  specify "13.7: Shared and Non-Shared Caches" do
+  end
+
+
+  specify "13.8: Errors or Incomplete Response Cache Behavior" do
+  end
+
+
+  specify "13.9: Side Effects of GET and HEAD" do
+  end
+
+
+  specify "13.10: Invalidation After Updates or Deletions" do
+  end
+
+
+  specify "13.11: Write-Through Mandatory" do
+  end
+
+
+  specify "13.12: Cache Replacement" do
+  end
+
+
+  specify "13.13: History Lists" do
+  end
+
+
+end

data/examples/mongrel_test_suite/test/http/connections.rb

@@ -0,0 +1,48 @@
+require 'rfuzz/session'
+
+context "8: Connections" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "8.1: Persistent Connections" do
+  end
+
+
+  specify "8.1.1: Purpose" do
+  end
+
+
+  specify "8.1.2: Overall Operation" do
+  end
+
+
+  specify "8.1.3: Proxy Servers" do
+  end
+
+
+  specify "8.1.4: Practical Considerations" do
+  end
+
+
+  specify "8.2: Message Transmission Requirements" do
+  end
+
+
+  specify "8.2.1: Persistent Connections and Flow Control" do
+  end
+
+
+  specify "8.2.2: Monitoring Connections for Error Status Messages" do
+  end
+
+
+  specify "8.2.3: Use of the 100 (Continue) Status" do
+  end
+
+
+  specify "8.2.4: Client Behavior if Server Prematurely Closes Connection" do
+  end
+
+
+end

data/examples/mongrel_test_suite/test/http/content_negotiation.rb

@@ -0,0 +1,20 @@
+require 'rfuzz/session'
+
+context "12: Content Negotiation" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "12.1: Server-driven Negotiation" do
+  end
+
+
+  specify "12.2: Agent-driven Negotiation" do
+  end
+
+
+  specify "12.3: Transparent Negotiation" do
+  end
+
+
+end

data/examples/mongrel_test_suite/test/http/entity.rb

@@ -0,0 +1,24 @@
+require 'rfuzz/session'
+
+context "7: Entity" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "7.1: Entity Header Fields" do
+  end
+
+
+  specify "7.2: Entity Body" do
+  end
+
+
+  specify "7.2.1: Type" do
+  end
+
+
+  specify "7.2.2: Entity Length" do
+  end
+
+
+end

data/examples/mongrel_test_suite/test/http/header_field_definitions.rb

@@ -0,0 +1,231 @@
+require 'rfuzz/session'
+
+context "14: Header Field Definitions" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "14.1: Accept" do
+  end
+
+
+  specify "14.2: Accept-Charset" do
+  end
+
+
+  specify "14.3: Accept-Encoding" do
+  end
+
+
+  specify "14.4: Accept-Language" do
+  end
+
+
+  specify "14.5: Accept-Ranges" do
+  end
+
+
+  specify "14.6: Age" do
+  end
+
+
+  specify "14.7: Allow" do
+  end
+
+
+  specify "14.8: Authorization" do
+  end
+
+
+  specify "14.9: Cache-Control" do
+  end
+
+
+  specify "14.9.1: What is Cacheable" do
+  end
+
+
+  specify "14.9.2: What May be Stored by Caches" do
+  end
+
+
+  specify "14.9.3: Modifications of the Basic Expiration Mechanism" do
+  end
+
+
+  specify "14.9.4: Cache Revalidation and Reload Controls" do
+  end
+
+
+  specify "14.9.5: No-Transform Directive" do
+  end
+
+
+  specify "14.9.6: Cache Control Extensions" do
+  end
+
+
+  specify "14.10: Connection" do
+  end
+
+
+  specify "14.11: Content-Encoding" do
+  end
+
+
+  specify "14.12: Content-Language" do
+  end
+
+
+  specify "14.13: Content-Length" do
+  end
+
+
+  specify "14.14: Content-Location" do
+  end
+
+
+  specify "14.15: Content-MD5" do
+  end
+
+
+  specify "14.16: Content-Range" do
+  end
+
+
+  specify "14.17: Content-Type" do
+  end
+
+
+  specify "14.18: Date" do
+  end
+
+
+  specify "14.18.1: Clockless Origin Server Operation" do
+  end
+
+
+  specify "14.19: ETag" do
+  end
+
+
+  specify "14.20: Expect" do
+  end
+
+
+  specify "14.21: Expires" do
+  end
+
+
+  specify "14.22: From" do
+  end
+
+
+  specify "14.23: Host" do
+  end
+
+
+  specify "14.24: If-Match" do
+  end
+
+
+  specify "14.25: If-Modified-Since" do
+  end
+
+
+  specify "14.26: If-None-Match" do
+  end
+
+
+  specify "14.27: If-Range" do
+  end
+
+
+  specify "14.28: If-Unmodified-Since" do
+  end
+
+
+  specify "14.29: Last-Modified" do
+  end
+
+
+  specify "14.30: Location" do
+  end
+
+
+  specify "14.31: Max-Forwards" do
+  end
+
+
+  specify "14.32: Pragma" do
+  end
+
+
+  specify "14.33: Proxy-Authenticate" do
+  end
+
+
+  specify "14.34: Proxy-Authorization" do
+  end
+
+
+  specify "14.35: Range" do
+  end
+
+
+  specify "14.35.1: Byte Ranges" do
+  end
+
+
+  specify "14.35.2: Range Retrieval Requests" do
+  end
+
+
+  specify "14.36: Referer" do
+  end
+
+
+  specify "14.37: Retry-After" do
+  end
+
+
+  specify "14.38: Server" do
+  end
+
+
+  specify "14.39: TE" do
+  end
+
+
+  specify "14.40: Trailer" do
+  end
+
+
+  specify "14.41: Transfer-Encoding" do
+  end
+
+
+  specify "14.42: Upgrade" do
+  end
+
+
+  specify "14.43: User-Agent" do
+  end
+
+
+  specify "14.44: Vary" do
+  end
+
+
+  specify "14.45: Via" do
+  end
+
+
+  specify "14.46: Warning" do
+  end
+
+
+  specify "14.47: WWW-Authenticate" do
+  end
+
+end

data/examples/mongrel_test_suite/test/http/http_message.rb

@@ -0,0 +1,122 @@
+require 'rfuzz/session'
+
+context "4: HTTP Message" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "4.1: Message Types" do
+    # In the interest of robustness, servers SHOULD ignore any empty line(s)
+    # received where a Request-Line is expected.
+  end
+
+
+  specify "4.2: Message Headers" do
+    # The field value MAY be preceded by any amount of LWS, though a single SP
+    # is preferred.
+
+    # leading or trailing LWS MAY be removed without changing the semantics of
+    # the field value
+
+    # Any LWS that occurs between field-content MAY be replaced with a single
+    # SP before interpreting the field value or forwarding the message
+    # downstream.
+    # RANT: WTF, so the values basically have to be quoted to prevent this?
+
+    # Multiple message-header fields with the same field-name MAY be present in
+    # a message if and only if the entire field-value for that header field is
+    # defined as a comma-separated list
+
+    # It MUST be possible to combine the multiple header fields into one
+    # "field-name: field-value" pair
+
+    # a proxy MUST NOT change the order of these field values when a message is
+    # forwarded
+  end
+
+
+  specify "4.3: Message Body" do
+    # Transfer-Encoding MUST be used to indicate any transfer-codings applied
+    # by an application to ensure safe and proper transfer of the message
+
+    # Transfer-Encoding MAY be added or removed by any application along the
+    # request/response chain 
+
+    # A message-body MUST NOT be included in a request if the specification of
+    # the request method (section 5.1.1) does not allow sending an entity-body
+    # in requests.
+
+    # A server SHOULD read and forward a message-body on any request 
+
+    # if the request method does not include defined semantics for an
+    # entity-body, then the message-body SHOULD be ignored when handling the
+    # request
+
+    # All responses to the HEAD request method MUST NOT include a message-body,
+    # even though the presence of entity- header fields might lead one to
+    # believe they do
+
+    # All 1xx (informational), 204 (no content), and 304 (not modified)
+    # responses MUST NOT include a message-body
+
+    # All other responses do include a message-body, although it MAY be of zero
+    # length.
+  end
+
+
+  specify "4.4: Message Length" do
+    # The Content-Length header field MUST NOT be sent if these two lengths are
+    # different (entity-length & transfer-length)
+
+    # If a message is received with both a Transfer-Encoding header field and a
+    # Content-Length header field, the latter MUST be ignored.
+
+    # "multipart/byteranges" media type MUST NOT be used unless the sender
+    # knows that the recipient can parse it
+
+    # Closing the connection cannot be used to indicate the end of a request
+    # body, since that would leave no possibility for the server to send back a
+    # response.
+
+    # HTTP/1.1 requests containing a message-body MUST include a valid
+    # Content-Length header field unless the server is known to be HTTP/1.1
+    # compliant
+
+    # If a request contains a message-body and a Content-Length is not given,
+    # the server SHOULD respond with 400 (bad request) if it cannot determine
+    # the length of the message, or with 411 (length required) if it wishes to
+    # insist on receiving a valid Content-Length.
+
+    # All HTTP/1.1 applications that receive entities MUST accept the "chunked"
+    # transfer-coding (section 3.6)
+    # RANT: Applications meaning what?  clients? servers? both?
+
+    # Messages MUST NOT include both a Content-Length header field and a
+    # non-identity transfer-coding.
+
+    # If the message does include a non- identity transfer-coding, the
+    # Content-Length MUST be ignored.  RANT: They already said that, must be
+    # really important.
+    #
+    # [Content-Length in messages which allow it] MUST exactly match the number
+    # of OCTETs in the message-body. 
+
+    # HTTP/1.1 user agents MUST notify the user when an invalid length is
+    # received and detected.
+  end
+
+
+  specify "4.5: General Header Fields" do
+    # These apply to both requests and responses:
+    # general-header = Cache-Control            ; Section 14.9
+    #                  | Connection               ; Section 14.10
+    #                  | Date                     ; Section 14.18
+    #                  | Pragma                   ; Section 14.32
+    #                  | Trailer                  ; Section 14.40
+    #                  | Transfer-Encoding        ; Section 14.41
+    #                  | Upgrade                  ; Section 14.42
+    #                  | Via                      ; Section 14.45
+    #                  | Warning                  ; Section 14.46
+  end
+
+end

data/examples/mongrel_test_suite/test/http/method_definitions.rb

@@ -0,0 +1,52 @@
+require 'rfuzz/session'
+
+context "9: Method Definitions" do
+  setup do
+    @sess = RFuzz::Session.new :host => "localhost", :port => 3000
+  end
+
+  specify "9.1: Safe and Idempotent Methods" do
+  end
+
+
+  specify "9.1.1: Safe Methods" do
+  end
+
+
+  specify "9.1.2: Idempotent Methods" do
+  end
+
+
+  specify "9.2: OPTIONS" do
+  end
+
+
+  specify "9.3: GET" do
+  end
+
+
+  specify "9.4: HEAD" do
+  end
+
+
+  specify "9.5: POST" do
+  end
+
+
+  specify "9.6: PUT" do
+  end
+
+
+  specify "9.7: DELETE" do
+  end
+
+
+  specify "9.8: TRACE" do
+  end
+
+
+  specify "9.9: CONNECT" do
+  end
+
+
+end