The initial HTTP request associated with this chunk
Incoming chunk of data for processing
Processing configuration
Data associated with this chunk
Processing configuration
Processing configuration
Netty channel associated with this request
Netty channel associated with this request
Timestamp when this event was fired
Timestamp when this event was fired
Number of milliseconds from the time when this context was created
Number of milliseconds from the time when this context was created
HTTP End point for this request
HTTP End point for this request
The initial HTTP request associated with this chunk
Store of items that can be used to pass data from route to processor and between processors.
Store of items that can be used to pass data from route to processor and between processors.
This map is not synchronized and not thread-safe. In most cases, we expect this cache to be used by a single thread - hence a standard map is faster.
If you do need to use a thread safe map, from your route, instance and store a ConcurrentHashMap
as an item
in this cache.
Incoming chunk of data for processing
Outgoing HTTP Response
Outgoing HTTP Response
Typically, the response should only be written if this is the last chunk. However, in the event of an error, you may wish to try to send a response back to the client.
Username of the authenticated user.
Username of the authenticated user. You need to set this for it to appear in the web logs.
Socko does not make assumptions on your authentication method. You do it and set this username
to let
us know.
Adds an entry to the web log
Adds an entry to the web log
If you have an authenticated user, be sure to set this.username
before writing a web log.
HTTP status code
length of response content in bytes
Event fired when a HTTP chunk is received
The org.mashupbots.socko.events.HttpChunkEvent will only be fired if:
isChunked
property is set toTrue
.The initial HTTP request associated with this chunk
Incoming chunk of data for processing
Processing configuration