Sandbox / Http
RequestBytesAsync
RequestBytesAsync(System.String,System.String,System.Net.Http.HttpContent,System.Collections.Generic.Dictionary`2<System.String,System.String>,System.Threading.CancellationToken) -> System.Threading.Tasks.Task`1<System.Byte[]> Overview
Declared callable operation; inspect inputs, outputs and linked evidence before using it.
Generated declaration summary
RequestBytesAsync declares the operation with recorded signature RequestBytesAsync(System.String,System.String,System.Net.Http.HttpContent,System.Collections.Generic.Dictionary`2<System.String,System.String>,System.Threading.CancellationToken) -> System.Threading.Tasks.Task`1<System.Byte[]>; runtime effects remain unverified.
Automatically derived from the pinned declaration; this is not a reviewed tutorial or runtime test.
Exact identity & snapshot
Parameters / inputs
| Name | Type | Modifiers | Default |
|---|---|---|---|
| requestUri | System.String | — | — |
| method | System.String | — | GET |
| content | System.Net.Http.HttpContent | — | null |
| headers | System.Collections.Generic.Dictionary`2<System.String,System.String> | — | null |
| cancellationToken | System.Threading.CancellationToken | — | null |
Result and evidenced effects
Declared return: System.Threading.Tasks.Task`1<System.Byte[]>. A void return is not evidence of no side effect; consult the linked source and workflow constraints.
Flow
The diagram separates the declared inputs, operation and result. Connections describe the recorded relationship; they do not establish execution order or lifecycle behaviour.
Open this operation in the flow explorer →
Examples
No reviewed code example or workflow covers this declaration. Use the exact declaration and inputs/outputs flow as the available local teaching surface, then run a bounded installed-build probe before relying on behaviour. Open the exact declaration flow.
Constraints and pitfalls
- Execution context: game-or-shared-unknown
- A public declaration is not proof of sandbox allowlisting.
- No compile/runtime verification was run.
Prerequisites and limits
- Resolve the declaring type and exact overload signature before relying on this declaration.
Still unknown
- Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.
declaration-and-sourcemetadata-and-source-only
Upstream documentation availability
No documentation was present in the selected record.
Evidence and verification
pinned metadata source correspondence unverified
- declaration: pinned-release-metadata
- implementation-source: engine/Sandbox.Engine/Utility/Web/Http.Requests.cs
Installed-build compile/runtime state: not run.
Related workflows
None selected.
Related diagrams
None selected.