A paranoid request library
A paranoid request library
Paranoid. Topology rendering.
Retry a request.
Paranoid text spacing for good readability, to automatically insert whitespace between CJK (Chinese, Japanese, Korean) and half-width characters (alphabetical letters, numerical digits and symbols).
Error class for Octokit request errors
Send parameterized requests to GitHub's APIs with sensible defaults in browsers and Node
Prisma extension for soft delete (paranoid pattern)
Adds paranoid deletion to a mongoose schema
[](https://www.npmjs.com/package/@aws-sdk/s3-request-presigner) [](https://www.npmjs.com/
Log all requests and request errors
A library of beautifully crafted react icons, perfect for enhancing the visual appeal and user experience of your web applications.
Like request, but smaller.
Core Promise support implementation for the simplified HTTP request client 'request'.
Tracks the download progress of a request made with mikeal/request, giving insight of various metrics including progress percent, download speed and time remaining
TypeScript definitions for request
Low-level HTTP/HTTPS/XHR/fetch request interception library.
Wrap native HTTP requests with RFC compliant cache support
utils for webpack loaders
This is a wrapper for jsoneditor package, it can be run offline without any dependencies and privacy concerns.
HTTP server mocking and expectations library for Node.js
Microsoft Azure SDK for JavaScript - Logger
Cypress's fork of a simplified HTTP request client.
Simplified HTTP request client.
This is a Strelka application plugin for describing rules for [Cross-Origin Resource Sharing (CORS)](http://www.w3.org/TR/cors/). NOTE: It's still a work in progress. By default, the plugin has paranoid defaults, and doesn't do anything. You'll need to grant access to the resources you want to share. To grant access, you declare one or more `access_control` blocks which can modify responses to matching access-control requests. All the blocks which match the incoming request's URI are called with the request and response objects in the order in which they're declared: # Allow access to all resources from any origin by default access_control do |req, res| res.allow_origin '*' res.allow_methods 'GET', 'POST' res.allow_credentials res.allow_headers :content_type end These are applied in the order you declare them, with each matching block passed the request if it matches. This happens before the application gets the request, so it can do any further modification it needs to, and so it can block requests from disallowed origins/methods/etc. There are a number of helper methods added to the request and response objects for applying and declaring access-control rules when this plugin is loaded:
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.