Long request path breaks requests table layout

[georgidhristov]

Description

When a request path is very long, the requests table creates horizontal overflow.

This makes the table hard to use because important columns like status and duration are pushed off-screen or hidden until the user scrolls horizontally.

Current Behavior

Long path values break Requests page layout

As a result:

• the table becomes wider than the page
• horizontal scrolling appears
• status and duration columns are no longer clearly visible
• the requests list looks broken on smaller screens or with long URLs/query strings

Screenshots

---

---

Expected Behavior

Long request paths should not break the table layout.

The status and duration columns should always remain visible.

Suggested Fix

Update the requests table layout so long paths are handled safely.

Possible options:

• truncate long paths with ellipsis
• allow path text to wrap
• keep status and duration columns fixed/visible
• show the full path in tooltip or details view

Result

After this change:

• long URLs no longer break the requests page
• status and duration remain visible
• the UI looks cleaner and easier to use
• debugging requests with long query strings is more usable