plug_response_header alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view plug_response_header alternatives based on common mentions on social networks and blogs.
-
commanded
Use Commanded to build Elixir CQRS/ES applications -
surface
A server-side rendering component library for Phoenix -
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 -
react_phoenix
Make rendering React.js components in Phoenix easy -
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 -
rummage_ecto
Search, Sort and Pagination for ecto queries -
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 -
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
recaptcha
A simple reCaptcha 2 library for Elixir applications. -
sentinel
DEPRECATED - Phoenix Authentication library that wraps Guardian for extra functionality -
plug_graphql
Plug (Phoenix) integration for GraphQL Elixir -
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. -
scrivener_headers
Scrivener pagination with headers and web linking -
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. -
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_statsd
Send connection response time and count to statsd -
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 -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host.
Free Global Payroll designed for tech teams
Do you think we are missing an alternative of plug_response_header or a related project?
README
PlugResponseHeader 
This Elixir plug allows manipulation of HTTP response headers:
- Deleting one or more HTTP response headers.
- Setting one or more HTTP response headers.
- Setting the HTTP "Server" response header.
This plug supports the following options. At least one option must be specified.
delete
: a bitstring or a list of bitstrings of header keys to be deleted.server
: convenience function forset: ["server": "MyServer"]
set
: a list of key/value pairs for headers to be set.
Setup
To use the plug in your projects, edit your mix.exs file and add the project as a dependency:
defp deps do
[
{:plug_response_header, "~> 0.2.1"}
]
end
Usage
pipeline :browser do
plug PlugResponseHeader,
delete: "x-request-id",
server: "MyServer",
set: [
"strict-transport-security": "max-age=31536000",
"cache-control": "no-transform"
]
...
end
License
*Note that all licence references and agreements mentioned in the plug_response_header README section above
are relevant to that project's source code only.