• Hi - sorry - only just spotted this here. I'll move it now.

    But as Ollie has said, it looks like the site only does HTTPS. Since the original Espruino doesn't have enough memory for HTTPS, I think it just ignores the https:// and tries with HTTP anyway - which is probably why you get the timeout?

  • Thanks for the replies and thanks for moving this over Gordon. I have been busy so only just got back to the investigation.

    So I tried to call to the SNI spec as Ollie suggested and this didn't work giving the same timeout exception was thrown -- Code below just in case others find this format useful

    require("http").get({
                            host: 'https://preview.gamesparks.net',
    				        path: '/callback/295737vYb5Kd/lamp/kPFrmFnPWrd­JuJ69M4DimgXxuhrVRefx/572a4047808eb904a0­8d149c'
    				    }, function(response) {
    				    	 console.log("Response: ",response);
    				        var body = '';
    					        response.on('data', function(d) {
    					            body += d;
    					        });   
    
    
    					     }
    

    Gordon you are correct in the fact I was recording a false positive by loading a text file to my secure domain and not realising the Expruino was just sending HTTP.

    I have a few Pico's but prefer the original espruino as my project uses more USART's than the Pico has available.

    Good to clarify there is no way the Original Board can do HTTPS

About

Avatar for fraser @fraser started