3

Github GitHub - projectdiscovery/simplehttpserver: Go alternative of python Simp...

 3 years ago
source link: https://github.com/projectdiscovery/simplehttpserver
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

SimpleHTTPserver

Go alternative of python SimpleHTTPServer

Features • Usage • Installation • Run SimpleHTTPserver • Join Discord

SimpleHTTPserver is a go enhanced version of the well known python simplehttpserver with in addition a fully customizable TCP server, both supporting TLS.

Features

  • HTTPS support
  • File server in arbitrary directory
  • Full request/response dump
  • Configurable ip address and listening port
  • Configurable HTTP/TCP server with customizable response via YAML template

Installing SimpleHTTPserver

SimpleHTTPserver requires go1.14+ to install successfully. Run the following command to get the repo -

▶ GO111MODULE=on go get -v github.com/projectdiscovery/simplehttpserver/cmd/simplehttpserver

Usage

simplehttpserver -h

This will display help for the tool. Here are all the switches it supports.

Flag Description Example listen Configure listening ip:port (default 127.0.0.1:8000) simplehttpserver -listen 127.0.0.1:8000 path Fileserver folder (default current directory) simplehttpserver -path /var/docs verbose Verbose (dump request/response, default false) simplehttpserver -verbose tcp TCP server (default 127.0.0.1:8000) simplehttpserver -tcp 127.0.0.1:8000 tls Enable TLS for TCP server simplehttpserver -tls rules File containing yaml rules simplehttpserver -rules rule.yaml upload Enable file upload in case of http server simplehttpserver -upload https Enable HTTPS in case of http server simplehttpserver -https cert HTTPS/TLS certificate (self generated if not specified) simplehttpserver -cert cert.pem key HTTPS/TLS certificate private key (self generated if not specified) simplehttpserver -key cert.key domain Domain name to use for the self-generated certificate simplehttpserver -domain projectdiscovery.io basic-auth Basic auth (username:password) simplehttpserver -basic-auth user:password realm Basic auth message simplehttpserver -realm "insert the credentials" version Show version simplehttpserver -version silent Show only results simplehttpserver -silent

Running simplehttpserver in the current folder

This will run the tool exposing the current directory on port 8000

▶ simplehttpserver 
2021/01/11 21:40:48 Serving . on http://0.0.0.0:8000/...
2021/01/11 21:41:15 [::1]:50181 "GET / HTTP/1.1" 200 383
2021/01/11 21:41:15 [::1]:50181 "GET /favicon.ico HTTP/1.1" 404 19

Running simplehttpserver in the current folder with HTTPS

This will run the tool exposing the current directory on port 8000 over HTTPS with user provided certificate:

▶ simplehttpserver -https -cert cert.pen -key cert.key
2021/01/11 21:40:48 Serving . on http://0.0.0.0:8000/...
2021/01/11 21:41:15 [::1]:50181 "GET / HTTP/1.1" 200 383
2021/01/11 21:41:15 [::1]:50181 "GET /favicon.ico HTTP/1.1" 404 19

Instead, to run with self-signed certificate and specific domain name:

▶ simplehttpserver -https -domain localhost
2021/01/11 21:40:48 Serving . on http://0.0.0.0:8000/...
2021/01/11 21:41:15 [::1]:50181 "GET / HTTP/1.1" 200 383
2021/01/11 21:41:15 [::1]:50181 "GET /favicon.ico HTTP/1.1" 404 19

Running simplehttpserver with basic auth and file upload

This will run the tool and will request the user to enter username and password before authorizing file uploads

▶ simplehttpserver -basic-auth root:root -upload
2021/01/11 21:40:48 Serving . on http://0.0.0.0:8000/...

To upload files use the following curl request with basic auth header:

▶ curl -v --user 'root:root' --upload-file file.txt http://localhost:8000/file.txt

Running TCP server with custom responses

This will run the tool as TLS TCP server and enable custom responses based on YAML templates:

▶ simplehttpserver -rule rules.yaml -tcp -tls -domain localhost

The rules are written as follows:

rules:
  - match: regex
    response: response data

For example to handle two different paths simulating an HTTP server or SMTP commands:

rules:
  # HTTP Requests
  - match: GET /path1
    response: |
              HTTP/1.0 200 OK
              Server: httpd/2.0
              x-frame-options: SAMEORIGIN
              x-xss-protection: 1; mode=block
              Date: Fri, 16 Apr 2021 14:30:32 GMT
              Content-Type: text/html
              Connection: close

              <HTML><HEAD><script>top.location.href='/Main_Login.asp';</script>
              </HEAD></HTML>
  - match: GET /path2
    response: |
              HTTP/1.0 404 OK
              Server: httpd/2.0
            
              <HTML><HEAD></HEAD><BODY>Not found</BODY></HTML>
  # SMTP Commands
  - match: "EHLO example.com"
    response: |
              250-localhost Nice to meet you, [127.0.0.1]
              250-PIPELINING
              250-8BITMIME
              250-SMTPUTF8
              250-AUTH LOGIN PLAIN
              250 STARTTLS
  - match: "MAIL FROM: <[email protected]>"
    response: 250 Accepted
  - match: "RCPT TO: <[email protected]>"
    response: 250 Accepted

Thanks

SimpleHTTPserver is made with black_heart by the projectdiscovery team.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK