dot-http for VS Code

An extension that behaves like a REST client. When you create a .http or .rest file, you can send HTTP requests and view the responses directly within the editor.

This project includes two components:

• VSCode extension — run .http files directly inside VS Code (this)
• CLI tool (dot-http) — run .http files from the terminal (see dot-http)

Features

• Send HTTP Requests — execute requests defined in .http or .rest files via a CodeLens button
• Variables — file variables (@var = value), .env files, system environment variables
• Multiple environments — switch env files per file using @env
• Request chaining — use response data from one request in another
• Assertions — assert status codes and response body/header values
• Cookie sessions — persist cookies across requests using @session
• GraphQL — automatic query wrapping
• Redirect control — per-request opt-out with # @no-follow
• Importing other files — share requests and variables across .http files

Usage Examples

Basic Request

GET https://jsonplaceholder.typicode.com/posts/1

Variables

@baseUrl = https://jsonplaceholder.typicode.com
@postId = 1

GET {{baseUrl}}/posts/{{postId}}

Variables can also come from a .env file in your workspace root or system environment:

GET {{baseUrl}}/posts?user={{$env USERNAME}}

Multiple Environments

Add @env at the top of your file to load a named env file:

@env = prod

###
GET {{API_URL}}/users

This loads prod.env from the workspace root instead of .env.

Request Chaining

# @name = getPost
GET https://jsonplaceholder.typicode.com/posts/1

###

# @requires = getPost
POST https://jsonplaceholder.typicode.com/posts
Content-Type: application/json

{
    "title": "New Post",
    "userId": {{getPost.body.userId}}
}

Available response fields:

• {{name.body.field}} — JSON body field (dot notation)
• {{name.headers.Content-Type}} — response header

Assertions

Use # @expect to assert the status code and # @assert for body/header checks. Results are shown in the response panel.

# @name = createUser
# @expect 201
# @assert body.name == John
# @assert header.Content-Type contains application/json
POST https://api.example.com/users
Content-Type: application/json

{"name": "John"}

Supported operators: ==, !=, contains, !contains

Assertion targets:

• status — HTTP status code
• body.<path> — JSON body field (dot notation)
• header.<Name> — response header value

Cookie Sessions

Add @session at the top of your file to persist cookies across requests:

@session = session.json

###
# @name = login
POST https://api.example.com/auth
Content-Type: application/json

{"username": "user", "password": "pass"}

###
# @requires = login
GET https://api.example.com/profile

The session file is saved relative to the workspace root.

GraphQL

Set Content-Type: application/graphql — the query is automatically wrapped as {"query": "..."} JSON:

POST https://api.example.com/graphql
Content-Type: application/graphql

{
  users {
    id
    name
  }
}

Redirect Control

By default redirects are followed (configurable via dot-http.followRedirects). To disable for a specific request:

# @no-follow
GET https://api.example.com/redirect

Importing Other Files

@import = auth.http

###
# @requires = login
GET https://api.example.com/profile
Authorization: Bearer {{login.body.token}}

• Paths are relative to the importing file's directory
• Imports are recursive; cyclic imports are safely skipped

Sending Files (Multipart/Form-Data)

POST https://httpbin.org/post
Content-Type: multipart/form-data; boundary=myBoundary

--myBoundary
Content-Disposition: form-data; name="file1"; filename="README.md"
Content-Type: text/markdown

< ./README.md
--myBoundary--

Extension Settings

Release Notes

0.9.0

Added environments, assertions, cookie sessions, GraphQL support, redirect control, timeout setting.

0.1.0

Initial release with variable handling, request chaining, and imports.