1.0.14 • Published 6 years ago

showserver v1.0.14

Weekly downloads
4
License
MIT
Repository
github
Last release
6 years ago

showserver

Node.js Express Server which does show the incoming request on the console.

Installation

$ npm install showserver --save

##How to use?

#!/usr/bin/env node

/**
 * Module dependencies.
 */
var showServer = require('showserver');

//Start server by either passing two arguments port for http and port for https or keep default ports 80,443
showServer.start(8080,8443);

How to run the server?

Before running the server you should ensure that the ports are open. In case you run on Ubuntu you would open the ports as follow:

$ sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT $ sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT

You can also check if the ports are already in use on Ubuntu as follow:

$ sudo lsof -i -P -n | grep LISTEN node 3331 root 11u IPv6 4289110 0t0 TCP :80 (LISTEN) node 3331 root 12u IPv6 4289111 0t0 TCP :443 (LISTEN)

If we assume that you did implement showserver inside the app.js file you can start it as follow:

$ node app.js

Note: In case you are using port 80 or 443 you maybe will need to use sudo to allow showServer to listen on this ports.

$ sudo node app.js

How to run from CLI?

In case you like to use showserver from the command line you will need to install it globally as follow:

$ sudo npm install showserver --g

NOTE: If you install showserver globally you will either need to use sudo or nvm, see here for further details: https://docs.npmjs.com/getting-started/fixing-npm-permissions

Afterwards you can just start it as follow:

$ sudo showserver

How to send request to the showServer?

you can test it via cURL on port 80. You can use whatever path you like to use, the outcome will always be the same: the showserver will just replay to you all the details about the HTTP request you did send:

curl http://sample.host.com/blablabla -v
*   Trying ::1...
* TCP_NODELAY set
* Connected to sample.host.com (::1) port 80 (#0)
> GET /blablabla HTTP/1.1
> Host: sample.host.com
> User-Agent: curl/7.58.0
> Accept: */*
> Pragma: akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/html; charset=utf-8
< Content-Length: 239
< ETag: W/"ef-pUR1aKRFi/PNg23STAv+vvimEg8"
< Date: Wed, 16 May 2018 17:09:42 GMT
< Connection: keep-alive
<
"/blablabla"
{
    "host": "localhost",
    "user-agent": "curl/7.58.0",
    "accept": "*/*",
    "pragma": "akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values"
* Connection #0 to host sample.host.com left intact
}

Same counts also for POST request:

curl -d test:test http://localhost/blablabla -v
*   Trying ::1...
* TCP_NODELAY set
* Connected to sample.host.com (::1) port 80 (#0)
> POST /blablabla HTTP/1.1
> Host: sample.host.com
> User-Agent: curl/7.58.0
> Accept: */*
> Pragma: akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values
> Content-Length: 9
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 9 out of 9 bytes
< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/html; charset=utf-8
< Content-Length: 347
< ETag: W/"15b-zyCJ3FIqEjbHUfsomTS+nHIyV4E"
< Date: Wed, 16 May 2018 17:10:05 GMT
< Connection: keep-alive
<
"/blablabla"
{
    "host": "sample.host.com",
    "user-agent": "curl/7.58.0",
    "accept": "*/*",
    "pragma": "akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values",
    "content-length": "9",
    "content-type": "application/x-www-form-urlencoded"
}
{
    "test:test": ""
* Connection #0 to host sample.host.com left intact
}

Hand you can do it even via HTTPS. IMPORTANT: Please not that showserver does use a self signed certificate which you will need to accept. In case of cURL we use the flag -k to ignor certification warnings:

curl -d test:test https://sample.host.com/blablabla -v -k
*   Trying ::1...
* TCP_NODELAY set
* Connected to sample.host.com (::1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /usr/local/etc/openssl/cert.pem
  CApath: /usr/local/etc/openssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=sample.host.com
*  start date: May 16 13:52:12 2018 GMT
*  expire date: May 16 13:52:12 2019 GMT
*  issuer: CN=sample.host.com
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
> POST /blablabla HTTP/1.1
> Host: sample.host.com
> User-Agent: curl/7.58.0
> Accept: */*
> Pragma: akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values
> Content-Length: 9
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 9 out of 9 bytes
< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/html; charset=utf-8
< Content-Length: 347
< ETag: W/"15b-zyCJ3FIqEjbHUfsomTS+nHIyV4E"
< Date: Wed, 16 May 2018 17:13:42 GMT
< Connection: keep-alive
<
"/blablabla"
{
    "host": "sample.host.com",
    "user-agent": "curl/7.58.0",
    "accept": "*/*",
    "pragma": "akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values",
    "content-length": "9",
    "content-type": "application/x-www-form-urlencoded"
}
{
    "test:test": ""
* Connection #0 to host sample.host.com left intact
}

How to rotate the Keys of the used Ceritificate?

NOTE: You will need to have openssl installed on your machine to make this operation work: 1. Create server certificate:

openssl req -x509 -passin pass:"test123" -passout pass:"test123" -newkey rsa:2048 -keyout tmp.key.pem -out cert.pem -days 365 -subj "/CN=sample.host.com"
  1. Remove password protection from key.pem:
openssl rsa -passin pass:"test123" -in tmp.key.pem -out key.pem && rm -f tmp.key.pem

FAQ

How did I know how to implement the CLI?

I used the followin tutorial from blog.npmjs.org to learn how to setup an CLI at Node.js: https://blog.npmjs.org/post/118810260230/building-a-simple-command-line-tool-with-npm

1.0.14

6 years ago

1.0.13

6 years ago

1.0.12

6 years ago

1.0.11

6 years ago

1.0.10

6 years ago

1.0.9

6 years ago

1.0.8

6 years ago

1.0.7

6 years ago

1.0.6

6 years ago

1.0.5

6 years ago

1.0.4

6 years ago

1.0.3

6 years ago

1.0.2

6 years ago

1.0.1

6 years ago

1.0.0

6 years ago