Fixed processing of the value x-forwarded-port.

Previously, when Weblocks was used along with lastest (after the 2019-09-07)
Woo server, this header lead to the 500 error.
Because behavior of the Woo was changed:

fukamachi/woo#84

Now Woo does not parses numberic headers and Weblocks has to do it itself.

A small fix to make it work with weblocks-websocket.

Merge branch 'reblocks' of github.com:40ants/weblocks into reblocks

Version 0.34.0

Added dependency on lack-middleware-session system because wee use it…

… to store sessions.

Request processing was streamlined and now weblocks/server:handle-req…

…uest does not contain non-local exits.

This fixes usage of the handle-request hook, because previously,
if you wrap some code around (call-next-hook), then part following
call-next-hook was ignored.

Version 0.33.0

A new hook was added - start-weblocks. It is called around the code i…

…n (weblocks/server:start) and can be used to setup some

Version 0.31.1

Version 0.31.0