Thanks for filing the issue!

Checked the issue on reported chrome version 64.0.3282.186 using windows 10 with the below mentioned steps.
1. Launched Chrome
2. Navigated to http://httpstat.us/
3. Opened DevTools-> Network -> Refreshed the page
4. Checked "status column"
As per your point no.5 in comment#0 tried to click on the mentioned values but we didn't observe any responses of 204 and 205. Attaching the screen cast of the same.

@Reporter: Could you please check the screen cast and clarify us on point no.5 of comment#0. Even we observed Devtools isn't displaying any response with 204 and 205 in status column. Any further inputs from your end may help us. 

Deleted: 816430.mp4 3.0 MB

	816430.mp4 3.0 MB View Download

hey!
https://www.screencast.com/t/ss8aIOaY

Click on this links. DevTools dont whow responses with 204 and 205 codes.

Deleted: 2018-03-05_20-50-17.png 4.5 KB

	2018-03-05_20-50-17.png 4.5 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue on reported chrome version 64.0.3282.186 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is not seen in latest canary 67.0.3362.0 Providing the reverse bisect info.

Reverse Bisect Info:
====================
Last Bad Build : 66.0.3346.0  Revision: 536238
First Good Build: 66.0.3347.0 Revision: 536620

You are probably looking for a change made after 536401 (known good), but no later than 536402 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/da651de72deefafe29d81c522234a2557475cc2b..30f8822a37972aabd4b76d4559d1062d6799c9cb

Suspecting the same from the above CL
Review URL: https://chromium-review.googlesource.com/912400

@Andrey Kosyakov: Please help in reassigning it to correct owner if this is not related to your change. And please clarify whether it is safe to merge the fix to M-66.
Note: Adding RB-Stable, Please feel free to remove if not applicable.

Thanks!

Friendly ping to get an update on this issue as it is marked as stable blocker.

Thanks..!

Still observing the same issue on latest stable-65.0.3325.181.
caseq@, Please take a look into this issue as it is marked as stable blocker.

Thanks..!

The fix is a large change that was followed up by several other fixes, we don't merge this kind of CLs to stable unless this is well justified by the severity of the problem, which is not the case here apparently. I'm removing RB-S from this bug.

(also closing since it's fixed on the tip of tree)