…oding: gzip'

…t that contains both HTTP headers and body as a single message

…ning to optimize it

…ncies

…f concurrency of receiver

… pressure on GC which reduce a lot of CPU usage and memory usage when receive hugh amount number of request

…h is very useful to allow user to disable a config

…mmit prevent confiction when using Authorization header for both JWT and Pulsar token and may be other authorization purpose.

Without this commit, using Authorization header as Pulsar token may cause memory leak because of token change per every request cause pulsar-beam to create a new pulsar client every time.
With configurable Authorization, user can also use ?includeHeader to get Authorization header to validate a payload without casuing pulsar-beam memory leak

…Request Line in the payload to send to Pulsar, which is useful in case of Pulsar consumer would like to detect the url or method that webhook client is using

…equestLine

…ation with a reverse proxy engine in front of or using other Authorization method.

This commit also add a short brief to let people know how to detect memory leak and resolve it. Further default configuration of Pulsar Beam should prevent this case from happening.