a tool help to setup server redirect support expose by localtunnel
Cycle.js driver for Node.js http server redirect
Check if a number is a redirect HTTP status code
Produces redirects (HTTP redirections) for pages in an Antora site.
A window.fetch polyfill.
Playwright Tools for MCP
Parses netlify redirects into a js object representation
MCP server that exercises all the features of the MCP protocol
Force a redirect to HTTPS when not on a local web server.
MJML: the only framework that makes responsive-email easy
Generate trusted local SSL/TLS certificates for local SSL development
Parses netlify redirects into a js object representation
hint for best practices related to HTTP redirects
Generate trusted local SSL/TLS certificates for local SSL development
MongoDB Model Context Protocol Server
Universal React avatar component makes it possible to generate avatars based on user information.
Library to assist with debugging HTTP(s) requests made by the request module.
MCP server for Context7
OAuth2 (SUSI) token creation plugin for @adobe/aio-lib-ims
Argo CD MCP Server
A plugin to add redirect URL functionality to Algolia Autocomplete.
Elegant Console Wrapper
An MCP server that fetches web pages and converts them to clean, readable Markdown.
WebSocket Matter server based on matter.js
Redirect server with dynamic URL and hostname support
Generate server redirects for Jekyll.
TrafficCop is a collection of test macros to test HTTP redirect rules for remote servers.
Generates server-specific files for handling redirects (e.g., .htaccess, firebase.json).
Micky makes simple HTTP requests (GET/HEAD), follows redirects, handles exceptions (invalid hosts/URIs, server errors, timeouts, redirect loops), automatically parses responses (JSON, etc.), is very lightweight, and has no dependency.
Desviar provides URL redirection; some possible applications include: - Web signup process - Continuous-deploy servers - Online ticket sales
ronin-vulns is a Ruby library for blind vulnerability testing. It currently supports testing for Local File Inclusion (LFI), Remote File Inclusion (RFI), SQL injection (SQLi), reflective Cross Site Scripting (XSS), Server Side Template Injection (SSTI), and Open Redirects.
With this library you can catch all outgoing e-mails and redirect them to a specific address. This is very useful for testing purpose, for example on your staging/testing server.
Bounces or redirects requests to missing static files. Could be useful when you want to run the server with production database locally and have user uploaded content fetched transparently from production site.
There are plenty of gems out there that deal with being an OAuth2 "consumer", where you redirect users to an OAuth2 "provider", allowing you to hand off authentication to a separate service. There are also plenty of gems that set you up as your own OAuth2 provider. ***BUT***, what happens when you want to separate your "authentication" server from your "resource" server? This gem is meant to be used on an API "resource" server, where you want to accept OAuth Access Tokens from a client, and validate them against a separate "authentication" server. This communication is outside the scope of the official OAuth 2 spec, but there is a need for it anyway.
This gem is like the `warden_openid_auth` gem, except that it only provides support for the very last step of the OAuth code flow, i.e. when the resource server / relying party (your Ruby Web app) validates the bearer token. Use this gem if your client-side Web (or mobile) app will be taking care of the rest of the OAuth2 motions, such as redirecting (or opening a popup window) to the authentication server at login time, managing and refreshing tokens, doing all these unspeakable things with iframes, etc.
A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.