Chrome Version       : 60.0.3112.101
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :

What steps will reproduce the problem?
1. Create a webapp reachable via http (say port 8080) and https (port 8443)
2. Log into webapp via http :8080, i.e. create insecure cookies (session cookie for example)
3. Cookie will be visible for http site and https "site", both sites will work fine.
4. Remove cookie and login again, this time via https :8443, creating a secure session cookie

What is the expected result?
All cookies matching to a host or domain are visible to a developer in the dev tools, regardless of the host's port and the cookie's path and secure flag. It's the developers task to understand which cookies are actually sent to a certain url of the host and he/she should be able to modify all of them.

What happens instead of that?
Cookies will be visible in dev tools via 8443 "site" but not 8080 "site".

The http :8080 site will be broken (endless login) because it cannot create insecure session cookies that overwrite the secure one. This is expected behaviour if you know of https://www.chromestatus.com/feature/4506322921848832. But if you don't and the developer is unable to debug or understand this due not seeing the blocking secure cookies (there is no console warning), it will create bug reports (as has happened here).

UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

There is a thread here: https://groups.google.com/forum/#!topic/google-chrome-developer-tools/rSbJ1m2F3HY

I will also attach screenshots
01 - logged in via http: insecure cookies created and visible in http :8080 site
02 - same view in https :8443 site - cookies visible
03 - removed cookies and logged in via https :8443: secure cookies created and visble in https :8443 site
04 - same view in http :8080 site - cookies not visible even though they exist and block insecure cookies


 

Deleted: 01-http.insecure.png 21.6 KB

	01-http.insecure.png 21.6 KB View Download

Deleted: 02-https.insecure.png 19.4 KB

	02-https.insecure.png 19.4 KB View Download

Deleted: 03-https.secure.png 21.1 KB

	03-https.secure.png 21.1 KB View Download

Deleted: 04-http.secure.png 17.0 KB

	04-http.secure.png 17.0 KB View Download