coder / coder/boundary

Test with an existing internal proxy

Open
#77 0 comments 0 reactions 0 assignees View on GitHub
low-priority
Dominant language
Go
Stars
25
Forks
7
PR merge metrics
No merged PRs in 30d

Description

### Problem statement
Customers with stringent security requirements often already have an internal proxy for managing and auditing network access. We need to ensure the allowlist for coder boundary complies with their existing configured proxy. Otherwise our target profile for boundary will experience difficulties on initial setup.

### Proposal
Set up a proxy `proxy.dev.coder.com` (not sure what this looks like) and test the HTTP allowlist in claude code with boundary.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.