In the Net panel a request of www.a.com/b/c?d=1 it's impossible to see "b"
Reported by
machineg...@gmail.com,
Apr 25 2017
|
|||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Steps to reproduce the problem:
1. Open the net panel
2. Perform an AJAX request
3. Try to view that request in the net panel
What is the expected behavior?
Let's say I have a URL like ...
http://www.example.com/foo/bar/1?baz=qux
I can use the "name" column to get "1?baz-qux". I can use the "domain" column to see "example.com". However, it is impossible for me to see "/foo/bar" unless I hover over the "name" column. This is very frustrating when you have a bunch of endpoints `foo/list`, `bar/list`, `baz/list`, etc. and all you can see in the tool is a bunch of rows that say "list".
One would expect that if they have requests from foo/bar and baz/bar that it would be possible to tell the two apart in the net panel.
What went wrong?
As I explained because there is no "path" column it's impossible to differentiate endpoints with the same final verb but differing parts of their earlier path.
Did this work before? No
Chrome version: 57.0.2987.133 Channel: n/a
OS Version: OS X 10.12.4
Flash Version:
I can't imagine this would be too hard, since you already have "name" and "domain" columns which are almost identical to "path", but it would make a huge difference to me (and to many other web devs I'm sure).
,
Apr 28 2017
,
Apr 28 2017
Oh, excellent suggestion. I'd still suggest that my original request is relevant, because: A) you still can't sort based on the middle part, because it appears under name, not as its own column B) It would also be easier to read as a separate column; consider: list?foo=bar 200 /foo/bar list?foo=bar 200 /bar/bar vs. list?foo=bar /foo/bar 20 list?foo=bar /bar/bar 200 (it's hard to fully capture the visual here with text, but hopefully you get the idea.) However, I definitely think the priority can be lowered since there is at least *some* way to see the path already. Thanks!
,
Apr 28 2017
Correct you cannot sort by directory, but that's what filter is designed to help with. The one thing that keeps sticking in my mind is: "why do the files have the same name when they have different content?" Yes sometimes it makes sense to have the same name for files, but generally it's considered good practice to prefix files with their component when they want to be named the same. If you really want a custom column, you can have the server send it as a custom header column and add it as a custom column in network panel. This will give even more flexibility for what you need. Keep in mind that this is not a common request and if we implement it, it means it makes it extremely difficult to do any UI/UX changes to keep reverse compatibility.
,
May 18 2017
> why do the files have the same name when they have different content?
They're not files, they're API endpoints. So for instance if I have a foo endpoint and a bar endpoint, each with different CRUD operations possible I'll have foo/create, foo/list, bar/create, bar/list, etc.
In the net panel though the one really useful bit of information in the URL ("foo" or "bar") is obscured, and all I can see is "list".
,
Jul 20 2017
Since we can currently show this data to users and if it's a huge pain point, we do have the ability for the server to send custom headers and add a custom column filtered on that key, I do not believe we will add this as a column. I do believe we should do something better, but I do not believe adding a new column for everyone (hidden or not) is the right approach. We already have a bit too many columns (imo) that are hidden and if we keep adding to the list, I'll take more time to enable the column than it would be to manually find the problem entries. Thanks for the suggestion/pain-point! |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@google.com
, Apr 28 2017