drewzboto / grunt-connect-proxy

Grunt Connect support for proxying API calls during development
MIT License
424 stars 122 forks source link

problem with self signed certificats #71

Open shayh opened 10 years ago

shayh commented 10 years ago

I have a self signed certificate on a https site I point the proxy to. I get the following error: Fatal error: Parse Error Fatal error: socket hang up

my configuration is:

proxies: [{
        context: '/api', // the context of the data service
        host: 'my-https-api-site', // wherever the data service is running
        port: 443,
        https: true,
        xforward: true,

      }],
livereload: {
        options: {
          open: {target: 'http://localhost:9000'},
          base: [
        '.tmp',
        '<%= yeoman.app %>'
        ],

please help, Shay

lukeman commented 10 years ago

I think your cert isn't the issue, as this is consistent with what I'm seeing. See #70 for SSL issues with 0.1.11. Downgrading to 0.1.10 worked for me.

paulsouche commented 10 years ago

Same issue here ! Downgrading worked for me too...

SyntaxStacks commented 10 years ago

I also had a similar issue where I would get a 400 with the message "HTTP request sent to a HTTPS port". After rolling back to 0.1.10 the error was resolved.

shayh commented 10 years ago

thanks, it does work in 0.1.10 after digging around it loos like a problem with the underling node-http-proxy that changed it's behavior after a certain version.

brianmriley commented 9 years ago

+1 worked for me too.

kaczynskid commented 9 years ago

Thx guys! Took me a while to find this page, but worked like a charm. Had HTTP 400: The plain HTTP request was sent to HTTPS port response and downgrading fixed it!

hummorsa commented 9 years ago

+1 in the downgrade ! after a day I found this page !

Stratus3D commented 9 years ago

Thanks everyone. Downgrading to version 0.1.10 worked for me as well.