Simple error http handling
Node.js mock / polyfill http object library for http req / res
Node.js mock / polyfill http object library for http req / res
Create a mock http object for stubbing and simulating ajax requests in tests.
An Object.keys replacement, in case Object.keys is not available. From https://github.com/es-shims/es5-shim
HTTP server cookie parsing and serialization
ES5 shim for ES6 (ECMAScript 6) Reflect and Proxy objects
minimal implementation of a PassThrough stream
Checks whether a value is an object
An HTTP(s) proxy `http.Agent` implementation for HTTP
A simple object to represent an http response
A response-like object for mocking a Node.js HTTP response stream
Create response http object with lmabda proxy integration
extend like a boss
Promisifies all the selected functions in an object
A promise based streaming tokenizer
Node Rest and Http Clients for use with TypeScript
Deep diffs two objects, including nested structures of arrays and objects, and return the difference.
The core `url` packaged standalone for use with Browserify.
Parses set-cookie headers into objects
Access deep object properties using a path
ProseMirror Markdown integration
option parsing and help generation
Copy a descriptor from object A to object B
Very simple http application framework, no special extras, just the basics. More documentation is coming!
Form objects on steroids for your HTTP API.
Convert Ruby HTTP request and client objects into their equivalent curl command. Useful for debugging and sharing HTTP requests.
Riaktor is a Ruby client and object mapper for Riak (http://riak.basho.com/). It's brand new and probably has bugs, but feel free to try it out.
Wrest is a fluent, easy-to-use, object oriented Ruby HTTP/REST client library with support for RFC2616 HTTP caching, multiple HTTP backends and async calls. It runs on CRuby and JRuby and is in production use at 10 * 🦄 scale.
Help create Collection+JSON hypermedia APIs
Messente enables you to send SMS messages from Ruby applications.
This gem transform the http response into a objects to access with dot instead brakets
The project is a Rack middleware to automatically log a HTTP request to a custom object.
simple object container for ruby
A Ruby client library for accessing CloudKit (http://getcloudkit.com) RESTful repositories using simple Ruby objects.
This is an experimental branch that implements a connection pool of Net::HTTP objects instead of a connection/thread. C/T is fine if you're only using your http threads to make connections but if you use them in child threads then I suspect you will have a thread memory leak. Also, I want to see if I get less connection resets if the most recently used connection is always returned. Also added a :force_retry option that if set to true will retry POST requests as well as idempotent requests. This branch is currently incompatible with the master branch in the following ways: * It doesn't allow you to recreate the Net::HTTP::Persistent object on the fly. This is possible in the master version since all the data is kept in thread local storage. For this version, you should probably create a class instance of the object and use that in your instance methods. * It uses a hash in the initialize method. This was easier for me as I use a HashWithIndifferentAccess created from a YAML file to define my options. This should probably be modified to check the arguments to achieve backwards compatibility. * The method shutdown is unimplemented as I wasn't sure how I should implement it and I don't need it as I do a graceful shutdown from nginx to finish up my connections. For connection issues, I completely recreate a new Net::HTTP instance. I was running into an issue which I suspect is a JRuby bug where an SSL connection that times out would leave the ssl context in a frozen state which would then make that connection unusable so each time that thread handled a connection a 500 error with the exception "TypeError: can't modify frozen". I think Joseph West's fork resolves this issue but I'm paranoid so I recreate the object. Compatibility with the master version could probably be achieved by creating a Strategy wrapper class for GenePool and a separate strategy class with the connection/thread implementation.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.