bolt alternatives and similar packages
Based on the "HTTP" category.
Alternatively, view bolt alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
-
-
-
-
-
spell
DISCONTINUED. Spell is a Web Application Messaging Protocol (WAMP) client implementation in Elixir. WAMP is an open standard WebSocket subprotocol that provides two application messaging patterns in one unified protocol: Remote Procedure Calls + Publish & Subscribe: http://wamp.ws/ -
web_socket
An exploration into a stand-alone library for Plug applications to easily adopt WebSockets. -
-
-
-
-
-
explode
An easy utility for responding with standard HTTP/JSON error payloads in Plug- and Phoenix-based applications -
Mechanize
DISCONTINUED. Build web scrapers and automate interaction with websites in Elixir with ease! -
SpiderMan
SpiderMan,a base-on Broadway fast high-level web crawling & scraping framework for Elixir. -
-
-
-
ivar
Ivar is an adapter based HTTP client that provides the ability to build composable HTTP requests. -
-
-
-
-
-
http_digex
HTTP Digest Auth Library to create auth header to be used with HTTP Digest Authentication -
-
-
InfluxDB high-performance time series database
Do you think we are missing an alternative of bolt or a related project?
README
Bolt :nut_and_bolt:
Bolt is a simple and fast http proxy living in the Erlang VM. Bolt can be used as a SSL proxy to prevent mixed content warnings on secure pages or to bypass CORS. For example as a SSL image proxy or html proxy for client side website scraping.
Installation
- Install dependencies with
mix deps.get - Start Phoenix endpoint with
mix phoenix.server
or
Usage
Pipe your requests through
http://example.com/?url=<url>
SSL
If you need to use your own certificate:
To launch your application with support for SSL, just place your keyfile and certfile in the priv directory and configure your router with the following options
# bolt/config/prod.exs
use Mix.Config
config :phoenix, Bolt.Endpoint,
https: [port: 443,
host: "example.com",
keyfile: System.get_env("SOME_APP_SSL_KEY_PATH"),
certfile: System.get_env("SOME_APP_SSL_CERT_PATH")],
...
When you include the otp_app option, Plug will search within the priv directory of your application. If you use relative paths for keyfile and certfile and do not include the otp_app option, Plug will throw an error.
You can leave out the otp_app option if you provide absolute paths to the files.
Example:
Path.expand("../../../some/path/to/ssl/key.pem", __DIR__)
Source: http://www.phoenixframework.org/v0.9.0/docs/configuration-for-ssl