Expose more in RequestContext

[kevmoo]

We can't (er, shouldn't?) expose the entire Request because we read the body.

But that leaves some things not accessible to custom and CloudEvent handlers

Including:

• requestedUri
• HTTP method
• protocol version

Follow-up to #108

[subfuzion]

Perhaps it's best to simply document that accessing the body is an error since the stream has already been read?

[kevmoo]

Perhaps it's best to simply document that accessing the body is an error since the stream has already been read?

Yeah. That makes this all a lot easier. Hrm...

Is there any (good) reason to hide the request otherwise?

[subfuzion]

I'm familiar with middleware (like the express json middleware) replacing the request body after parsing the stream so that it can be accessed. Since body is dynamic, can our wrapper (or can we create a wrapper to) override?

[subfuzion]

But if I understood your question correctly, I don't think we can anticipate all the reasons why someone wants access to the raw request, so I don't recommend making it completely inaccessible. However, it might not be bad to explore the idea of using a scope as @simolus3 suggested here (although for a different reason), to make the request object a bit less conspicuous (only need to be aware about it if you really want it)...