Closed lostintangent closed 7 years ago
I agree @lostintangent. In fact, we already do filter some things to prevent the "observer effect". These just need to be removed.
It's fairly straightforward to not display any X-Glimpse-*
headers. There's an open question on whether we want to have a button to "show hidden headers".
open question on whether we want to have a button to "show hidden headers".
Let's not worry about that for now.
👍
This is now available in Glimpse for Node 0.16.4. Please see our announcement issue for more information.
Data filtering is always tricky, so I'm not sure if this is even the right decision, but it seems somewhat strange to see a cookie and response header in each request entry, that were introduced because of Glimpse. We did a lot of filtering in the F12 network tool, because we wanted to prevent the "observer effect" as much as possible, but I'm not sure whether that is a goal of yours. On one side, you can optimize for accuracy, ala Fiddler, and display the actual over-the-wire request/response, but I can't help but feel like Glimpse wants to be optimized for intuition/simplicity/etc., and therefore, stripping out stuff like this could be valuable to prevent unnecessary clutter.
I think this is pretty low-pri, but I just wanted to log it, since when we worked on the F12 profilers, we tended to err on the side of data filtering in order to project the most curated experience as possible, that was still actionable. For data that isn't important to end-users, we tried to remove it as much as possible.