BUG Legacy /targets links redirect to Home instead of Target Registry
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Inspect frontend/src/App.tsx around lines 614-625 and 674, then reproduce the routing behavior by opening /targets in the frontend or with the provided Playwright steps. Add the compatibility redirect so /targets reaches /registry/targets instead of the wildcard Home route, and verify the resulting pathname.
Written by the indexing model from the issue text.
Description
Describe the bug
The target-management route moved from /targets to /registry/targets, but the application does not preserve the old route as a compatibility redirect. Opening a saved /targets link falls through to the wildcard route and silently redirects to Home (/) instead of the Target Registry.
This was reproduced on commit 6fd719317c09228cb332cacf5d76b6602610b591. Fresh searches across open issues and pull requests found no matching report. Open PR #2699 was also inspected; it does not add the missing redirect.
Relevant source: frontend/src/App.tsx:614-625,674.
Steps/Code to Reproduce
- Start the frontend.
- Navigate directly to
/targets, which was the canonical target-management route before the Converter Registry change. - Wait for application routing to settle.
- Observe that the URL becomes
/and Home is displayed.
await page.goto('/targets');
console.log(new URL(page.url()).pathname);
// Actual: '/'
// Expected: '/registry/targets'
Expected Results
The legacy /targets route should redirect to /registry/targets, preserving bookmarks, documentation links, browser history, and user intent.
For example:
<Route path="/targets" element={<Navigate to="/registry/targets" replace />} />
Actual Results
The wildcard route redirects /targets to /. Home is shown with no explanation, and the Target Registry is not visible.
Users can recover by opening Registry manually, but existing links silently lose their destination.
Screenshots
N/A. The URL transition and visible Home route are deterministic from the steps above.
Versions
- OS: Windows
- Browser: Chromium through Playwright 1.63.0
- Node: 25.7.0
- Python: 3.14.4
- PyRIT:
1.2.0.dev0, commit6fd719317c09228cb332cacf5d76b6602610b591 - Python package inventory: N/A; this is a frontend routing defect.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 896
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 155
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PyRIT
-
Bug: triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
BUG: ScorerMetrics.to_json() raises TypeError on the trial_scores array ScorerEvaluator attaches Open
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
Bug: triage help wanted
Difficulty 3/5 1-2 days Newbie friendliness 75/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100