cors_plug alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view cors_plug alternatives based on common mentions on social networks and blogs.
-
ex_admin
ExAdmin is an auto administration package for Elixir and the Phoenix Framework -
phoenix_html
Phoenix.HTML functions for working with HTML strings and templates -
phoenix_ecto
Phoenix and Ecto integration with support for concurrent acceptance testing -
absinthe_plug
Plug support for Absinthe, the GraphQL toolkit for Elixir -
phoenix_live_reload
Provides live-reload functionality for Phoenix -
params
Easy parameters validation/casting with Ecto.Schema, akin to Rails' strong parameters. -
phoenix_pubsub_redis
The Redis PubSub adapter for the Phoenix framework -
dayron
A repository `similar` to Ecto.Repo that maps to an underlying http client, sending requests to an external rest api instead of a database -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
sentinel
DEPRECATED - Phoenix Authentication library that wraps Guardian for extra functionality -
plug_rails_cookie_session_store
Rails compatible Plug session store -
phx_component_helpers
Extensible Phoenix liveview components, without boilerplate -
filterable
Filtering from incoming params in Elixir/Ecto/Phoenix with easy to use DSL. -
multiverse
Elixir package that allows to add compatibility layers via API gateways. -
access pass
provides a full user authentication experience for an API. Includes login,logout,register,forgot password, forgot username, confirmation email and all that other good stuff. Includes plug for checking for authenticated users and macro for generating the required routes. -
scrivener_headers
Scrivener pagination with headers and web linking -
better_params
Cleaner request parameters in Elixir web applications ๐ -
phoenix_pubsub_rabbitmq
RabbitMQ adapter for Phoenix's PubSub layer -
plug_checkup
PlugCheckup provides a Plug for adding simple health checks to your app -
plug_rest
REST behaviour and Plug router for hypermedia web applications in Elixir -
Votex
Implements vote / like / follow functionality for Ecto models in Elixir. Inspired from Acts as Votable gem in Ruby on Rails -
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
phoenix_html_simplified_helpers
Some helpers for phoenix html( truncate, time_ago_in_words, number_with_delimiter, url_for, current_page? ) -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host.
Learn Elixir in as little as 12 Weeks
Do you think we are missing an alternative of cors_plug or a related project?
README
CorsPlug
An Elixir Plug to add Cross-Origin Resource Sharing (CORS).
Usage
Add this plug to your mix.exs
dependencies:
def deps do
# ...
{:cors_plug, "~> 2.0"},
#...
end
When used together with the awesomeness that's the Phoenix Framework
please note that putting the CORSPlug
in a pipeline won't work as they are only invoked for
matched routes.
I therefore recommend to put it in lib/your_app/endpoint.ex
:
defmodule YourApp.Endpoint do
use Phoenix.Endpoint, otp_app: :your_app
# ...
plug CORSPlug
plug YourApp.Router
end
Alternatively you can add options routes to your scope and CORSPlug
to your pipeline, as
suggested by @leighhalliday
pipeline :api do
plug CORSPlug
# ...
end
scope "/api", PhoenixApp do
pipe_through :api
resources "/articles", ArticleController
options "/articles", ArticleController, :options
options "/articles/:id", ArticleController, :options
end
Compatibility
Whenever I get around to, I will bump the plug dependency to the latest version of plug. This will ensure compatibility with the latest plug versions.
As of Elixir and Open Telecom Platform (OTP), my goal is to test against the three most recent versions respectively.
Configuration
This plug will return the following headers:
On preflight (OPTIONS
) requests:
- Access-Control-Allow-Origin
- Access-Control-Allow-Credentials
- Access-Control-Max-Age
- Access-Control-Allow-Headers
- Access-Control-Allow-Methods
On GET
, POST
, etc. requests:
- Access-Control-Allow-Origin
- Access-Control-Expose-Headers
- Access-Control-Allow-Credentials
You can configure allowed origins using one of the following methods:
Using a list
Lists can now be comprised of strings, regexes or a mix of both:
plug CORSPlug, origin: ["http://example1.com", "http://example2.com", ~r/https?.*example\d?\.com$/]
Using a regex
plug CORSPlug, origin: ~r/https?.*example\d?\.com$/
Using the config.exs file
config :cors_plug,
origin: ["http://example.com"],
max_age: 86400,
methods: ["GET", "POST"]
Using a function/0
or function/1
that returns the allowed origin as a string
Caveat: Anonymous functions are not possible as they can't be quoted.
plug CORSPlug, origin: &MyModule.my_fun/0
def my_fun do
["http://example.com"]
end
plug CORSPlug, origin: &MyModule.my_fun/1
def my_fun(conn) do
# Do something with conn
["http://example.com"]
end
send_preflight_response?
There may be times when you would like to retain control over the response sent to OPTIONS requests. If you
would like CORSPlug to only set headers, then set the send_preflight_response?
option to false.
plug CORSPlug, send_preflight_response?: false
# or in the app config
config :cors_plug,
send_preflight_response?: false
Please note that options passed to the plug overrides app config but app config overrides default options.
Please find the list of current defaults in [cors_plug.ex](lib/cors_plug.ex#L5:L26).
As per the W3C Recommendation
the string null
is returned when no configured origin matched the request.
License
Copyright 2020 Michael Schaefermeyer
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.
*Note that all licence references and agreements mentioned in the cors_plug README section above
are relevant to that project's source code only.