RubyGems - browsed - Versions diffs - 0.3.0 → 0.3.6 - Mend

browsed 0.3.0 → 0.3.6

Files changed (162) hide show

data/lib/browsed/proxies/proxy-chain-server/node_modules/proxy-chain/CHANGELOG.md DELETED

@@ -1,109 +0,0 @@
-0.2.7 / 2018-02-19
-===================
-- Updated README
-0.2.6 / 2018-12-27
-===================
-- Bugfix: Added `Host` header to `HTTP CONNECT` requests to upstream proxies
-0.2.5 / 2018-09-10
-===================
-- Bugfix: Invalid request headers broke proxy chain connection. Now they will be skipped instead.
-0.2.4 / 2018-07-27
-===================
-- Bugfix: large custom responses were not delivered completely because the socket was closed too early
-0.2.3 / 2018-06-21
-===================
-- Bugfix: 'requestFailed' was emitting `{ request, err }` instead of `{ request, error }`
-0.2.2 / 2018-06-19
-===================
-- BREAKING: The 'requestFailed' event now emits object `{ request, error }` instead of just `error`
-0.1.35 / 2018-06-12
-===================
-- Bugfix: When target URL cannot be parsed instead of crashing, throw RequestError
-0.1.34 / 2018-06-08
-===================
-- Minor improvement: HandlerBase.fail() now supports RequestError
-0.1.33 / 2018-06-08
-===================
-- Renamed `customResponseFunc` to `customResponseFunction` and changed parameters for more clarity
-0.1.32 / 2018-06-08
-===================
-- Added `customResponseFunc` option to `prepareRequestFunction` to support custom response to HTTP requests
-0.1.31 / 2018-05-21
-===================
-- Updated project homepage in package.json
-0.1.29 / 2018-04-15
-===================
-- Fix: anonymizeProxy() now supports upstream proxies with empty password
-0.1.28 / 2018-03-27
-===================
-- Added `createTunnel()` function to create tunnels through HTTP proxies for arbitrary TCP network connections
-  (eq. connection to mongodb/sql database through HTTP proxy)
-0.1.27 / 2018-03-05
-===================
-- Better error messages for common network errors
-- Pass headers from target socket in HTTPS tunnel chains
-0.1.26 / 2018-02-14
-===================
-- If connection is denied because of authentication error, optionally "prepareRequestFunction" can provide error message.
-0.1.25 / 2018-02-12
-===================
-- When connection is only through socket, close srcSocket when trgSocket ends
-0.1.24 / 2018-02-09
-===================
-- Fixed incorrect closing of ServerResponse object which caused phantomjs to mark resource requests as errors.
-0.1.23 / 2018-02-07
-===================
-- Fixed missing variable in "Incorrect protocol" error message.
-0.1.22 / 2018-02-05
-===================
-- Renamed project's GitHub organization
-0.1.21 / 2018-01-26
-===================
-- Added Server.getConnectionIds() function
-0.1.20 / 2018-01-26
-===================
-- Fixed "TypeError: The header content contains invalid characters" bug
-0.1.19 / 2018-01-25
-===================
-- fixed uncaught error events, code improved
-0.1.18 / 2018-01-25
-===================
-- fixed a memory leak, improved logging and consolidated code
-0.1.17 / 2018-01-23
-===================
-- added `connectionClosed` event to notify users about closed proxy connections
-0.1.16 / 2018-01-09
-===================
-- added measuring of proxy stats - see `getConnectionStats()` function
-0.1.14 / 2017-12-19
-===================
-- added support for multiple headers with the same name (thx shershennm)
-0.0.1 / 2017-11-06
-===================
-- Project created

data/lib/browsed/proxies/proxy-chain-server/node_modules/proxy-chain/LICENSE DELETED

@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-   1. Definitions.
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-   END OF TERMS AND CONDITIONS
-   APPENDIX: How to apply the Apache License to your work.
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "{}"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-   Copyright 2018 Apify Technologies s.r.o.
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-       http://www.apache.org/licenses/LICENSE-2.0
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

data/lib/browsed/proxies/proxy-chain-server/node_modules/proxy-chain/README.md DELETED

@@ -1,278 +0,0 @@
-# Programmable HTTP proxy server for Node.js
-[![npm version](https://badge.fury.io/js/proxy-chain.svg)](http://badge.fury.io/js/proxy-chain)
-[![Build Status](https://travis-ci.org/apifytech/proxy-chain.svg)](https://travis-ci.org/apifytech/proxy-chain)
-Node.js implementation of a proxy server (think Squid) with support for SSL, authentication, upstream proxy chaining,
-custom HTTP responses and measuring traffic statistics.
-The authentication and proxy chaining configuration is defined in code and can be dynamic.
-Note that the proxy server only supports Basic authentication
-(see [Proxy-Authorization](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Proxy-Authorization) for details).
-For example, this package is useful if you need to use proxies with authentication
-in the headless Chrome web browser, because it doesn't accept proxy URLs such as `http://username:password@proxy.example.com:8080`.
-With this library, you can set up a local proxy server without any password
-that will forward requests to the upstream proxy with password.
-The package is used for this exact purpose by the [Apify web scraping platform](https://www.apify.com).
-To learn more about the rationale behind this package,
-read [How to make headless Chrome and Puppeteer use a proxy server with authentication](https://medium.com/@jancurn/how-to-make-headless-chrome-and-puppeteer-use-a-proxy-server-with-authentication-249a21a79212).
-## Run a simple HTTP/HTTPS proxy server
-```javascript
-const ProxyChain = require('proxy-chain');
-const server = new ProxyChain.Server({ port: 8000 });
-server.listen(() => {
-    console.log(`Proxy server is listening on port ${8000}`);
-});
-```
-## Run a HTTP/HTTPS proxy server with credentials and upstream proxy
-```javascript
-const ProxyChain = require('proxy-chain');
-const server = new ProxyChain.Server({
-    // Port where the server will listen. By default 8000.
-    port: 8000,
-    // Enables verbose logging
-    verbose: true,
-    // Custom function to authenticate proxy requests and provide the URL to chained upstream proxy.
-    // It must return an object (or promise resolving to the object) with the following form:
-    // { requestAuthentication: Boolean, upstreamProxyUrl: String }
-    // If the function is not defined or is null, the server runs in simple mode.
-    // Note that the function takes a single argument with the following properties:
-    // * request      - An instance of http.IncomingMessage class with information about the client request
-    //                  (which is either HTTP CONNECT for SSL protocol, or other HTTP request)
-    // * username     - Username parsed from the Proxy-Authorization header. Might be empty string.
-    // * password     - Password parsed from the Proxy-Authorization header. Might be empty string.
-    // * hostname     - Hostname of the target server
-    // * port         - Port of the target server
-    // * isHttp       - If true, this is a HTTP request, otherwise it's a HTTP CONNECT tunnel for SSL
-    //                  or other protocols
-    // * connectionId - Unique ID of the HTTP connection. It can be used to obtain traffic statistics.
-    prepareRequestFunction: ({ request, username, password, hostname, port, isHttp, connectionId }) => {
-        return {
-            // Require clients to authenticate with username 'bob' and password 'TopSecret'
-            requestAuthentication: username !== 'bob' || password !== 'TopSecret',
-            // Sets up an upstream HTTP proxy to which all the requests are forwarded.
-            // If null, the proxy works in direct mode, i.e. the connection is forwarded directly
-            // to the target server.
-            upstreamProxyUrl: `http://username:password@proxy.example.com:3128`,
-        };
-    },
-});
-server.listen(() => {
-  console.log(`Proxy server is listening on port ${server.port}`);
-});
-// Emitted when HTTP connection is closed
-server.on('connectionClosed', ({ connectionId, stats }) => {
-  console.log(`Connection ${connectionId} closed`);
-  console.dir(stats);
-});
-// Emitted when HTTP request fails
-server.on('requestFailed', ({ request, error }) => {
-  console.log(`Request ${request.url} failed`);
-  console.error(error);
-});
-```
-## Measuring traffic statistics
-To get traffic statistics for a certain HTTP connection, you can use:
-```javascript
-const stats = server.getConnectionStats(connectionId);
-console.dir(stats);
-```
-The resulting object looks like:
-```javascript
-{
-    srcTxBytes: Number,
-    srcRxBytes: Number,
-    trgTxBytes: Number,
-    trgRxBytes: Number,
-}
-```
-## Custom responses
-Custom responses allow you to override the response to a HTTP requests to the proxy, without contacting any target host.
-For example, this is useful if you want to provide a HTTP proxy-style interface
-to an external API or respond with some custom page to certain requests.
-Note that this feature is only available for HTTP connections. That's because HTTPS
-connections cannot be intercepted without access to the target host's private key.
-To provide a custom response, the result of the `prepareRequestFunction` function must
-define the `customResponseFunction` property, which contains a function that generates the custom response.
-The function is passed no parameters and it must return an object (or a promise resolving to an object)
-with the following properties:
-```javascript
-{
-  // Optional HTTP status code of the response. By default it is 200.
-  statusCode: 200,
-  // Optional HTTP headers of the response
-  headers: {
-    'X-My-Header': 'bla bla',
-  }
-  // Optional string with the body of the HTTP response
-  body: 'My custom response',
-  // Optional encoding of the body. If not provided, defaults to 'UTF-8'
-  encoding: 'UTF-8',
-}
-```
-Here is a simple example:
-```javascript
-const ProxyChain = require('proxy-chain');
-const server = new ProxyChain.Server({
-    port: 8000,
-    prepareRequestFunction: ({ request, username, password, hostname, port, isHttp }) => {
-        return {
-            customResponseFunction: () => {
-                return {
-                    statusCode: 200,
-                    body: `My custom response to ${request.url}`,
-                };
-            },
-        };
-    },
-});
-server.listen(() => {
-  console.log(`Proxy server is listening on port ${server.port}`);
-});
-```
-## Closing the server
-To shut down the proxy server, call the `close([destroyConnections], [callback])` function. For example:
-```javascript
-server.close(true, () => {
-  console.log('Proxy server was closed.');
-});
-```
-The `closeConnections` parameter indicates whether pending proxy connections should be forcibly closed.
-If the `callback` parameter is omitted, the function returns a promise.
-## Helper functions
-The package also provides several utility functions.
-### `anonymizeProxy(proxyUrl, callback)`
-Parses and validates a HTTP proxy URL. If the proxy requires authentication,
-then the function starts an open local proxy server that forwards to the proxy.
-The port is chosen randomly.
-The function takes an optional callback that receives the anonymous proxy URL.
-If no callback is supplied, the function returns a promise that resolves to a String with
-anonymous proxy URL or the original URL if it was already anonymous.
-The following example shows how you can use a proxy with authentication
-from headless Chrome and [Puppeteer](https://github.com/GoogleChrome/puppeteer).
-For details, read this [blog post](https://blog.apify.com/how-to-make-headless-chrome-and-puppeteer-use-a-proxy-server-with-authentication-249a21a79212).
-```javascript
-const puppeteer = require('puppeteer');
-const proxyChain = require('proxy-chain');
-(async() => {
-    const oldProxyUrl = 'http://bob:password123@proxy.example.com:8000';
-    const newProxyUrl = await proxyChain.anonymizeProxy(oldProxyUrl);
-    // Prints something like "http://127.0.0.1:45678"
-    console.log(newProxyUrl);
-    const browser = await puppeteer.launch({
-        args: [`--proxy-server=${newProxyUrl}`],
-    });
-    // Do your magic here...
-    const page = await browser.newPage();
-    await page.goto('https://www.example.com');
-    await page.screenshot({ path: 'example.png' });
-    await browser.close();
-})();
-```
-### `closeAnonymizedProxy(anonymizedProxyUrl, closeConnections, callback)`
-Closes anonymous proxy previously started by `anonymizeProxy()`.
-If proxy was not found or was already closed, the function has no effect
-and its result is `false`. Otherwise the result is `true`.
-The `closeConnections` parameter indicates whether pending proxy connections are forcibly closed.
-The function takes an optional callback that receives the result Boolean from the function.
-If callback is not provided, the function returns a promise instead.
-### `createTunnel(proxyUrl, targetHost, options, callback)`
-Creates a TCP tunnel to `targetHost` that goes through a HTTP proxy server
-specified by the `proxyUrl` parameter.
-The result of the function is a local endpoint in a form of `hostname:port`.
-All TCP connections made to the local endpoint will be tunneled through the proxy to the target host and port.
-For example, this is useful if you want to access a certain service from a specific IP address.
-The tunnel should be eventually closed by calling the `closeTunnel()` function.
-The `createTunnel()` function accepts an optional Node.js-style callback that receives the path to the local endpoint.
-If no callback is supplied, the function returns a promise that resolves to a String with
-the path to the local endpoint.
-Example:
-```javascript
-const host = await createTunnel('http://bob:pass123@proxy.example.com:8000', 'service.example.com:356');
-// Prints something like "localhost:56836"
-console.log(host);
-```
-### `closeTunnel(tunnelString, closeConnections, callback)`
-Closes tunnel previously started by `createTunnel()`.
-The result value is `false` if the tunnel was not found or was already closed, otherwise it is `true`.
-The `closeConnections` parameter indicates whether pending connections are forcibly closed.
-The function takes an optional callback that receives the result of the function.
-If the callback is not provided, the function returns a promise instead.
-### `parseUrl(url)`
-Calls Node.js's [url.parse](https://nodejs.org/docs/latest/api/url.html#url_url_parse_urlstring_parsequerystring_slashesdenotehost)
-function and extends the resulting object with the following fields: `scheme`, `username` and `password`.
-For example, for `HTTP://bob:pass123@example.com` these values are
-`http`, `bob` and `pass123`, respectively.
-### `redactUrl(url, passwordReplacement)`
-Takes a URL and hides the password from it. For example:
-```javascript
-// Prints 'http://bob:<redacted>@example.com'
-console.log(redactUrl('http://bob:pass123@example.com'));
-```