Request Bodies
piespector currently supports these request body types:
NoneForm-Datax-www-form-urlencodedRawGraphQLBinary
Body type details
Section titled “Body type details”No request body is sent.
Form-Data
Section titled “Form-Data”Use key/value rows in the Body section.
Supported interaction:
j/kto move rowsH/Lto move between key and valuee/Enterto editato add a rowspaceto enable or disable a rowdto delete a row
x-www-form-urlencoded
Section titled “x-www-form-urlencoded”Uses the same row-based interaction as Form-Data.
Values are URL-encoded when the request is sent.
Raw supports these subtypes:
TextJSONXMLHTMLJavaScript
Raw is edited from two rows in the Body section:
Body TypeRaw Format
The actual text then opens in the full text editor.
GraphQL
Section titled “GraphQL”GraphQL is a dedicated body type with its own editor mode.
The current behavior sends the editor content as a raw GraphQL document with the GraphQL content type.
Binary
Section titled “Binary”Binary uses a file path instead of a large text body.
The body field is path-oriented:
- it edits a filesystem path inline
Tabcompletes matching paths- repeated
Tabcycles matching files and folders
When sent, piespector reads the file bytes from that path. Relative paths resolve from the current working directory.
Raw body validation
Section titled “Raw body validation”piespector validates body text before sending when the selected subtype or effective content type implies a structured format.
JSONXMLHTMLJavaScriptGraphQL
Validation is intended to catch structural mistakes before the request goes out.
Default content types
Section titled “Default content types”If you do not set an explicit Content-Type header, piespector infers one from the body:
Raw / JSON:application/jsonRaw / XML:application/xmlRaw / HTML:text/htmlRaw / JavaScript:application/javascriptRaw / Text:text/plainGraphQL:application/graphqlBinary:application/octet-streamForm-Data:multipart/form-data; boundary=...x-www-form-urlencoded:application/x-www-form-urlencoded
If you add an explicit Content-Type header, that explicit header wins. The inferred auto header can also be disabled from Headers.
Syntax highlighting
Section titled “Syntax highlighting”Syntax highlighting is available in previews and editors for:
JSONXMLHTMLJavaScriptGraphQL
Editing behavior
Section titled “Editing behavior”Body editing depends on the active body type:
- row-based for
Form-Dataandx-www-form-urlencoded - full text editor for raw text-heavy bodies and
GraphQL - inline path editing for
Binary
Method interaction
Section titled “Method interaction”GET and HEAD requests do not send a body, even if body fields are populated in the editor.