ghebby/request_inspector repository overview

⁠Introduction

Need to inspect requests from third-party services with unclear documentation? This application offers a straightforward tool to examine HTTP request headers and payloads. Simply generate a session, use the provided URL as the endpoint for the request you wish to analyze, and view the detailed request header and payload on the session page.

⁠Usage

Try the live instance of this application at request_inspector⁠. Create a session and use any HTTP client (e.g., curl, Postman) to send a request to the provided URL. The request headers and payloads will be displayed on the session page. Sessions last one hour and can handle up to five requests. To prevent abuse, throttling limits requests to 10/request/minute. Requests are stored in memory and are not saved to disk or a database, disappearing when the session expires or is terminated.

⁠Installation

When working with highly sensitive data, it is recommended to host your own instance of this application. The application is built using the Go programming language and can run on any platform that supports Go. For the best security, consider installing by compiling the source code. This ensures that the code you are running matches the code in the repository. A Linux-compiled binary is also provided for convenience.

⁠As Docker Container (Recommended)

To run the application as a Docker container, you will need Docker and Docker Compose installed on your system. Then you can create a docker-compose.yml file with the following content:

version: '3'

services:
  inspector:
    image: ghebby/request_inspector:0.0.1
    restart: unless-stopped  
    environment:
      - TZ=Europe/Rome
      - PORT=9001
    ports:
      # host:container
      - 9099:9001

Run docker-compose up -d to start the application. The application will be available on port 9099 of the host machine. Run docker-compose down to stop the application.

I you need https support, consider adding a reverse proxy like Nginx or Apache in front of the application, the best way is to add a container with the reverse proxy to the docker-compose.yml file, run them in the same docker network and configure the reverse proxy to forward the requests to the application container.