## TL;DR

Upgrade to Teleport v14 or later. The fix shipped in v14 (via PR #27761, released in 14.0.0), and two reporters confirmed the 501s on POST/XHR went away after upgrading to v14, with no extra reverse proxy needed.

## Steps

1. - The app works with direct access but breaks through Teleport.
- The failures are 501s on POST/XHR specifically.
- You are on Teleport v13 or earlier.

2. If all three hold, upgrade to v14+ rather than adding a reverse proxy or
reworking the app.

## When to use

You are seeing this: Web applications accessed through Teleport Application Access behave differently than direct access: some POST requests (XHR calls) come back with 501 responses, breaking app functionality. Use this skill when you run into "Teleport Application Access: POST/XHR requests return 501".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Teleport 11.1.3, 14.0.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
