Skip to content

need to redirect to a http server from https url? you can deploy this in a small server and url it to point to any url

License

Notifications You must be signed in to change notification settings

arunsai63/ssl-anywhere

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SSL-Anywhere

SSL-Anywhere is a lightweight HTTPS proxy server that enables secure access to HTTP endpoints. It serves as a bridge between HTTPS clients and HTTP servers, allowing you to maintain secure communication even when dealing with HTTP-only services.

Problem Statement

Many legacy systems, internal services, or third-party APIs still operate over HTTP. However, modern security requirements often mandate HTTPS communication. SSL-Anywhere solves this challenge by providing a secure HTTPS endpoint that can safely proxy requests to HTTP services.

Features

  • Seamless HTTPS to HTTP proxying
  • Preserves all HTTP methods (GET, POST, PUT, DELETE, etc.)
  • Maintains query parameters and request bodies
  • Forwards headers while ensuring proper host management
  • Supports streaming responses
  • Simple deployment and configuration

Installation

# Clone the repository
git clone https://github.com/arunsai63/ssl-anywhere.git

# Install dependencies
cd ssl-anywhere
npm install

Usage

  1. Start the server:
node server.js
  1. Access HTTP endpoints through the proxy:
https://your-domain.com/http://target-service.com/api/endpoint

Example:

// Original HTTP request
fetch('http://api.example.com/data')

// Using SSL-Anywhere
fetch('https://your-domain.com/http://api.example.com/data')

Configuration

The server runs on port 8005 by default. Modify the PORT constant in server.js to change this.

For production deployment, we recommend using Nginx or similar as a reverse proxy to handle SSL termination.

Security Considerations

  • SSL-Anywhere does not perform certificate validation for target HTTP services
  • Ensure your deployment follows security best practices for proxy servers
  • Consider implementing request filtering and rate limiting for production use
  • Monitor proxy usage and implement appropriate access controls

Use Cases

  • Accessing HTTP-only APIs from HTTPS websites
  • Legacy system integration
  • Development and testing environments
  • Internal services requiring HTTPS compliance

Contributing

Contributions are welcome! Please feel free to submit pull requests.

  1. Fork the repository
  2. Create your feature branch
  3. Commit your changes
  4. Push to the branch
  5. Submit a pull request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Disclaimer

This tool is provided as-is without any guarantees. Users should evaluate their security requirements before implementing in production environments.

About

need to redirect to a http server from https url? you can deploy this in a small server and url it to point to any url

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published