Html proxy on line

configurable-http-proxy

configurable-http-proxy (CHP) provides you with a way to update and manage a proxy table using a command line interface or REST API. It is a simple wrapper around node-http-proxy. node-http-proxy is an HTTP programmable proxying library that supports websockets and is suitable for implementing components such as reverse proxies and load balancers. By wrapping node-http-proxy, configurable-http-proxy extends this functionality to JupyterHub deployments.

Table of Contents

Install

If you’re installing configurable-http-proxy in Linux, you can follow the instruction of nodesource to install arbitrary version of Node.js.

To install the configurable-http-proxy package globally using npm:

npm install -g configurable-http-proxy

To install from the source code found in this GitHub repo:

git clone https://github.com/jupyterhub/configurable-http-proxy cd configurable-http-proxy npm install # Use 'npm install -g' for global install

Usage

The configurable proxy runs two HTTP(S) servers:

• The public-facing interface to your application (controlled by —ip , —port )
  • listens on all interfaces by default.
  • listens on localhost by default
  • The REST API uses token authorization, where the token is set in the CONFIGPROXY_AUTH_TOKEN environment variable.

  

  Starting the proxy

  configurable-http-proxy [options]

  where [options] are the command-line options described below.

  Setting a default target

  The default target is used when a client has requested a URL for which there is no routing target found in the proxy table. To set a default target, pass the command line option, —default-target , when starting the configurable proxy:

  configurable-http-proxy --default-target=proto://host[:port]

  configurable-http-proxy --default-target=http://localhost:8888

  Command-line options

  Usage: configurable-http-proxy [options] Options: -V, --version output the version number --ip Public-facing IP of the proxy --port (defaults to 8000) Public-facing port of the proxy --ssl-key SSL key to use, if any --ssl-cert SSL certificate to use, if any --ssl-ca SSL certificate authority, if any --ssl-request-cert Request SSL certs to authenticate clients --ssl-reject-unauthorized Reject unauthorized SSL connections (only meaningful if --ssl-request-cert is given) --ssl-protocol Set specific SSL protocol, e.g. TLSv1_2, SSLv3 --ssl-ciphers `:`-separated ssl cipher list. Default excludes RC4 --ssl-allow-rc4 Allow RC4 cipher for SSL (disabled by default) --ssl-dhparam SSL Diffie-Helman Parameters pem file, if any --api-ip Inward-facing IP for API requests (default: "localhost") --api-port Inward-facing port for API requests (defaults to --port=value+1) --api-ssl-key SSL key to use, if any, for API requests --api-ssl-cert SSL certificate to use, if any, for API requests --api-ssl-ca SSL certificate authority, if any, for API requests --api-ssl-request-cert Request SSL certs to authenticate clients for API requests --api-ssl-reject-unauthorized Reject unauthorized SSL connections (only meaningful if --api-ssl-request-cert is given) --client-ssl-key SSL key to use, if any, for proxy to client requests --client-ssl-cert SSL certificate to use, if any, for proxy to client requests --client-ssl-ca SSL certificate authority, if any, for proxy to client requests --client-ssl-request-cert Request SSL certs to authenticate clients for API requests --client-ssl-reject-unauthorized Reject unauthorized SSL connections (only meaningful if --client-ssl-request-cert is given) --default-target Default proxy target (proto://host[:port]) --error-target Alternate server for handling proxy errors (proto://host[:port]) --error-path Alternate server for handling proxy errors (proto://host[:port]) --redirect-port Redirect HTTP requests on this port to the server on HTTPS --redirect-to Redirect HTTP requests from --redirect-port to this port --pid-file Write our PID to a file --no-x-forward Don't add 'X-forward-' headers to proxied requests --no-prepend-path Avoid prepending target paths to proxied requests --no-include-prefix Don't include the routing prefix in proxied requests --auto-rewrite Rewrite the Location header host/port in redirect responses --change-origin Changes the origin of the host header to the target URL --protocol-rewrite Rewrite the Location header protocol in redirect responses to the specified protocol --custom-header Custom header to add to proxied requests. Use same option for multiple headers (--custom-header k1:v1 --custom-header k2:v2) (default: <>) --insecure Disable SSL cert verification --host-routing Use host routing (host as first level of path) --metrics-ip IP for metrics server (default: "0.0.0.0") --metrics-port Port of metrics server. Defaults to no metrics server --log-level Log level (debug, info, warn, error) (default: "info") --timeout Timeout (in millis) when proxy drops connection for a request. --proxy-timeout Timeout (in millis) when proxy receives no response from target. --storage-backend Define an external storage class. Defaults to in-MemoryStore. -h, --help display help for command 

  Using the REST API

  The configurable-http-proxy REST API is documented and available as:

  REST API Basics

  HTTP method	Endpoint	Function
  GET	/api/	API Root

  HTTP method	Endpoint	Function
  GET	/api/routes	Get all routes in routing table
  POST	/api/routes/	Add a new route
  DELETE	/api/routes/	Remove the given route

  Authenticating via passing a token

  The REST API is authenticated via passing a token in the Authorization header. The API is served under the /api/routes base URL.

  For example, this curl command entered in the terminal passes this header «Authorization: token $CONFIGPROXY_AUTH_TOKEN» for authentication and retrieves the current routing table from this endpoint, http://localhost:8001/api/routes :

  curl -H "Authorization: token $CONFIGPROXY_AUTH_TOKEN" http://localhost:8001/api/routes

  Getting the routing table

  GET /api/routes[?inactive_since=ISO8601-timestamp] 

  inactive_since : If the inactive_since URL parameter is given as an ISO8601 timestamp, only routes whose last_activity is earlier than the timestamp will be returned. The last_activity timestamp is updated whenever the proxy passes data to or from the proxy target.

  A JSON dictionary of the current routing table. This JSON dictionary excludes the default route.

  The current routing table is returned to the user if the request is successful.

  Adding new routes

  POST requests create new routes. The body of the request should be a JSON dictionary with at least one key: target , the target host to be proxied.

  Required input:

  After adding the new route, any request to /path/prefix on the proxy’s public interface will be proxied to target .

  Deleting routes

  Removes a route from the proxy’s routing table.

  Custom error pages

  Custom error pages can be provided when the proxy encounters an error and has no proxy target to handle a request. There are two typical errors that CHP may hit, along with their status code:

  • 404 error: Returned when a client has requested a URL for which there is no routing target. This error can be prevented by setting a default target before starting the configurable-http-proxy.
  • 503 error: Returned when a route exists, but the upstream server isn’t responding. This is more common, and can be due to any number of reasons, including the target service having died, not finished starting, or network instability.

  Setting the path for custom error pages

  When starting the CHP, specify an error path —error-path /usr/share/chp-errors to the location of the error page:

  configurable-http-proxy --error-path /usr/share/chp-errors

  When a proxy error occurs, CHP will look in the following location for a custom html error page to serve:

  where is a status code number for an html page to serve. If there is a 503 error, CHP will look for a custom error page in this location /usr/share/chp-errors/503.html .

  If no custom error html file exists for the error code, CHP will use the default error.html . If you specify an error path, make sure you also create a default error.html file.

  Setting a target for custom error handling

  You can specify a target URL to use when errors occur by setting —error-target when starting the CHP.

  If, for example, CHP starts with —error-target http://localhost:1234 , and the proxy encounters an error, the proxy will make a GET request to the error-target server. The GET request will be sent to the error-target server URL, http://localhost:1234 , appending the status code / , and passing the failing request’s URL escaped in a URL parameter:

  GET /404?url=%2Fescaped%2Fpath 

  Host-based routing

  If the CHP is started with the —host-routing option, the proxy will use the hostname of the incoming request to select a target.

  When using host-based routes, the API uses the target in the same way as if the hostname were the first part of the URL path, e.g.:

  < "/example.com": "https://localhost:1234", "/otherdomain.biz": "http://10.0.1.4:5555", >

  Troubleshooting

  Q: My proxy is not starting. What could be happening?

  • If this occurs on Ubuntu/Debian, check that the you are using a recent version of node. Some versions of Ubuntu/Debian come with a version of node that is very old, and it is necessary to update node to a recent or LTS version.

  Источник

  Бесплатный прокси для любого устройства

  CroxyProxy использует передовые технологии для обеспечения лучшей поддержки современных веб-приложений. По сравнению с другими онлайн-прокси, он не нарушает работу веб-сайтов и поддерживает потоковое видео и аудио, авторизацию, комментарии и другие функции. Вот почему это лучший бесплатный прокси на рынке. Он позволяет искать в Google, получать доступ к Youtube, общаться с друзьями на Facebook и использовать Twitter.

  CroxyProxy — это бесплатный прокси, который защищает вашу конфиденциальность. Он изменяет ваше местоположение и делает вас невидимым при работе в Интернете. Мы шифруем все данные перед их передачей вам, даже старые веб-сайты без SSL передаются через безопасное соединение. Наши серверы расположены в разных странах ЕС, поэтому вы можете получить доступ к большинству веб-сайтов.

  Возможности веб-прокси

  • CroxyProxy защищает вашу конфиденциальность. Ваш настоящий IP-адрес становится невидимым.
  • Генерация постоянной ссылки. Вы можете отправить ссылку своим друзьям.
  • Он поддерживает любые ОС и любые устройства, поддерживается большинство веб-браузеров: Chrome, Firefox, Safari.
  • Это позволяет безопасно открывать незашифрованные веб-сайты.
  • Базовая версия бесплатна.

  Лучшая защита конфиденциальности

  CroxyProxy — хорошая альтернатива VPN. По сравнению с VPN трафик веб-прокси не может быть обнаружен. Вы даже можете открыть одну веб-страницу через прокси и направить другой трафик. И, наконец, вы можете сэкономить деньги, так как это бесплатная услуга.

  CroxyProxy очень прост в использовании, вам не нужно загружать какое-либо приложение или настраивать браузер. Он поддерживает различные типы устройств и операционных систем: настольные компьютеры Windows, мобильные устройства на Android, Chromebook и т. Д.

  Просто введите свой поисковый запрос в форму выше и получите безопасный доступ к любому веб-сайту, который вам нужен!

  Источник

  Читайте также:  Make connection with database in php