Skip to content

Document spin-client-addr header as optional #112

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 7, 2025
Merged

Document spin-client-addr header as optional #112

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/v1/http-trigger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -278,7 +278,7 @@ As well as any headers passed by the client, Spin sets several headers on the re
| `spin-raw-component-route` | The component route pattern matched, as written in the component manifest (that is, _excluding_ the base, but including the wildcard indicator if present) | `/users/...` |
| `spin-component-route` | The component route pattern matched, _excluding_ any wildcard indicator | `/users` |
| `spin-base-path` | The application base path | `/shop` |
| `spin-client-addr` | The IP address and port of the client | `127.0.0.1:53152` |
| `spin-client-addr` | The IP address and port of the client. Some Spin runtimes do not set this header. | `127.0.0.1:53152` |

### Inside HTTP Components

Expand Down
2 changes: 1 addition & 1 deletion content/v2/http-trigger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -362,7 +362,7 @@ As well as any headers passed by the client, Spin sets several headers on the re
| `spin-raw-component-route` | The component route pattern matched, as written in the component manifest (that is, _excluding_ the base, but including the wildcard indicator if present) | `/users/:userid/cart/...` |
| `spin-component-route` | The component route pattern matched, _excluding_ any wildcard indicator | `/users/:userid/cart` |
| `spin-base-path` | The application base path | `/shop` |
| `spin-client-addr` | The IP address and port of the client | `127.0.0.1:53152` |
| `spin-client-addr` | The IP address and port of the client. Some Spin runtimes do not set this header. | `127.0.0.1:53152` |

### Inside HTTP Components

Expand Down
2 changes: 1 addition & 1 deletion content/v3/http-trigger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -355,7 +355,7 @@ As well as any headers passed by the client, Spin sets several headers on the re
| `spin-matched-route` | The part of the trigger route that was matched by the route (including the wildcard indicator if present) | `/users/:userid/cart/...` |
| `spin-raw-component-route` | The component route pattern matched, including the wildcard indicator if present | `/users/:userid/cart/...` |
| `spin-component-route` | The component route pattern matched, _excluding_ any wildcard indicator | `/users/:userid/cart` |
| `spin-client-addr` | The IP address and port of the client | `127.0.0.1:53152` |
| `spin-client-addr` | The IP address and port of the client. Some Spin runtimes do not set this header. | `127.0.0.1:53152` |

### Inside HTTP Components

Expand Down