New issue
Advanced search Search tips

Issue 830522 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 821492
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

http2 push not working when using local generated cert

Reported by jokcy...@gmail.com, Apr 9 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. 
generate cert by `openssl req -x509 -newkey rsa:2048 -nodes -sha256 -subj '/CN=localhost' \
  -keyout localhost-privkey.pem -out localhost-cert.pem`

nodejs 9.11.1 with server.js code here
```
const http2 = require('http2');
const fs = require('fs');

const server = http2.createSecureServer({
  key: fs.readFileSync('localhost-privkey.pem'),
  cert: fs.readFileSync('localhost-cert.pem')
});
server.on('error', (err) => console.error(err));
server.on('socketError', (err) => console.error(err));

server.on('stream', (stream, headers) => {
  // stream is a Duplex
  if (headers[':path'] === '/') {
    stream.respond({
      'content-type': 'text/html',
      ':status': 200
    });
    stream.pushStream({ ':path': '/test.js' }, (err, pushStream) => {
      pushStream.on('error', console.error)
      pushStream.respond({
        ':status': 200,
        'content-type': 'application/javascript' 
      });
      pushStream.end('alert("push success")');  
    });
    stream.end('<h1>Hello World</h1><script src="/test.js"></script>');
  }
});

server.listen(8443);
```
start up by `node server.js`
2. view https://locahost:8443 in chrome. ignore no secure infos
3. no 'push success' alerted

What is the expected behavior?
alert 'push success'

What went wrong?
it seems push refused by chrome via no secure https cert.

I tested in safari and firefox both of them worked.

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
Labels: Needs-Triage-M65
Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET TE-NeedsTriageHelp
This issue seems to be out of scope for triaging from our end as this is related to certificates and algorithms hence adding label TE-NeedsTriageHelp and requesting someone from dev team to have a look into this and help in further triaging it.

Thanks!

Comment 3 by mmenke@chromium.org, Apr 11 2018

Components: -Platform>DevTools Internals>Network>HTTP2

Comment 4 by b...@chromium.org, Apr 12 2018

Mergedinto: 821492
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment