vatsrahul1001 opened a new pull request, #67091:
URL: https://github.com/apache/airflow/pull/67091

   Backport of #66690 to `v3-2-test` for the 3.2.2 release.
   
   Regression fix for [#46533](https://github.com/apache/airflow/issues/46533): 
when Airflow UI is reached through a proxy (Gitpod, Codespaces, ngrok, reverse 
proxies), the auth-failure redirect was preserving the API server's absolute 
URL in the \`next\` parameter, so users could be bounced to the wrong origin 
(e.g. \`http://localhost:29091\`) after login. The fix routes the redirect 
through a new \`getNextHref()\` helper that constructs a same-origin relative 
target (\`pathname + search + hash\`).
   
   ### Backport notes
   
   Conflict in \`airflow-core/src/airflow/ui/src/utils/links.test.ts\` resolved 
as follows:
   
   - Upstream PR's test file imports/exercises both \`getNextHref\` (added by 
this PR) and \`getSafeExternalUrl\` (added by an earlier PR not on v3-2-test). 
Dropped the \`describe(\"getSafeExternalUrl\", ...)\` suite and its import — 
kept only the \`getNextHref\` test suite that this PR actually introduces.
   - Added \`/* eslint-disable max-lines */\` to the test file because 
v3-2-test still has the older 250-line cap (PR #66124 raises it to 500 on main 
but isn't backported here). The directive matches the existing precedent in 
\`airflow-core/src/airflow/ui/rules/typescript.js:1\`.
   
   \`main.tsx\` and \`links.ts\` auto-merged cleanly with only the 
\`getNextHref\` changes.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Opus 4.7 (1M context)
   
   Generated-by: Claude Opus 4.7 (1M context) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to