Skip to content
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

Updates pages to remove outdated k8s notice #1334

Merged
merged 1 commit into from
Mar 28, 2024
Merged

Updates pages to remove outdated k8s notice #1334

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
4 changes: 1 addition & 3 deletions content/docs/reference/access-log-fields.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,9 +110,7 @@ The table below lists all available access log fields:
| `upstream-cluster` | The cluster the request was sent to (the cluster name is assigned by Pomerium, for example `route-3bb74f76f9d71f9c` or `pomerium-control-plane-http`) | Yes |
| `user-agent` | The User-Agent field sent by the user's browser | Yes |
| `query` | The HTTP request query (for example, `?test=one&other=13`) | No |
| \* [`headers.{CustomHeaderName}`](#custom-headers-fields) | An HTTP Request Header identified by the `HeaderName` (for example, `headers.X-Amzn-Trace-Id` might return `Root=1-64c03960-37809588421513e42f260f56`) | No |

\* The `headers.{CustomHeaderName}` field is only available in **Core** and **Enterprise**, not Kubernetes.
| [`headers.{CustomHeaderName}`](#log-custom-headers-fields) | An HTTP Request Header identified by the `HeaderName` (for example, `headers.X-Amzn-Trace-Id` might return `Root=1-64c03960-37809588421513e42f260f56`) | No |

:::danger

Expand Down
4 changes: 1 addition & 3 deletions content/docs/reference/authorize-log-fields.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ The table below lists all available authorize log fields:
| `check-request-id` | The request ID of the gRPC check call | Yes |
| `email` | The logged-in user's email address | Yes |
| `headers` | The complete set of HTTP request headers | No |
| \* `headers.{CustomHeaderName}` | An HTTP Request Header identified by the `HeaderName` | No |
| [`headers.{CustomHeaderName}`](#log-custom-headers-fields) | An HTTP Request Header identified by the `HeaderName` | No |
| `host` | The HTTP request `:authority` or `Host` header value. Can be a domain name or IP address and may contain a port number (for example, `www.example.com`) | Yes |
| `id-token` | The user's ID token | No |
| `id-token-claims` | The user's ID token claims | No |
Expand All @@ -119,8 +119,6 @@ The table below lists all available authorize log fields:
| `session-id` | the session ID | Yes |
| `user` | The user's ID | Yes |

\* The `headers.{CustomHeaderName}` field is only available in **Core** and **Enterprise**, not Kubernetes.

:::danger

Query parameters often contain sensitive information. Do not enable the `query` log field without careful consideration.
Expand Down
Loading