Fiddler will not intercept curl traffic by default. You&#39;ll need to specify the `-x` proxy option. If curl displays an SSL error message, additionally use the `-k` option to disable SSL validation.

    curl -x 127.0.0.1:8888 -k www.example.com

I have tried a number of methods to no avail. I have data in terms of a date (YYYY-MM-DD) and am trying to get in terms of just the month and year, such as: MM-YYYY or YYYY-MM.

Ultimately, I would like it to look like this:

    ID    Date         Month_Yr
    1     2004-02-06   2004-02
    2     2006-03-14   2006-03
    3     2007-07-16   2007-07
    ...   ...          ...

I am doing this in hopes of plotting money earned on average in a month, from a number of orders, over a period of time. Any help, or a push in the right direction would be much appreciated. 


Extract Month and Year From Date in R

I received VmWare image from my client for some testing purposes. I need to convert it to Hyper-V. 
I followed steps in http://www.askme4tech.com/how-convert-vmware-virtual-machine-hyper-v. I installed Microsoft Virtual Machine Converter and started to convert virtual disks in PowerShell. However I&#39;m getting eror:


    C:\Windows\system32&gt; ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath &quot;c:\temp\disk2.vmdk&quot; -DestinationLiteralPath &quot;c:\data\HyperV\PH\&quot; -VhdType DynamicHardDisk -VhdFormat Vhdx

    ConvertTo-MvmcVirtualHardDisk : The entry 1 is not a supported disk database entry for the descriptor.
    At line:1 char:1
    + ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath &quot;c:\temp\disk2.vmdk&quot;
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (Microsoft.Accel...nversionService:DriveConversionService) [ConvertTo-MvmcVirtualHardDisk], VmdkDescriptorParseException
        + FullyQualifiedErrorId : DiskConversion,Microsoft.Accelerators.Mvmc.Cmdlet.Commands.ConvertToMvmcVirtualHardDiskCommand
    
    ConvertTo-MvmcVirtualHardDisk : One or more errors occurred.
    At line:1 char:1
    + ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath &quot;c:\temp\disk2.vmdk&quot;
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (Microsoft.Accel...nversionService:DriveConversionService) [ConvertTo-MvmcVirtualHardDisk], AggregateException
        + FullyQualifiedErrorId : DiskConversion,Microsoft.Accelerators.Mvmc.Cmdlet.Commands.ConvertToMvmcVirtualHardDiskCommand


Error when converting VmWare virtual disk to HyperV

Why doesn&#39;t Fiddler show `curl` traffic? Other traffic gets displayed, just not `curl`. How can I get fiddler to intercept `curl` traffic?

Why Doesn&#39;t Fiddler Show Curl Traffic?

<p>Why doesn't Fiddler show <code>curl</code> traffic? Other traffic gets displayed, just not <code>curl</code>. How can I get fiddler to intercept <code>curl</code> traffic?</p>


The new version 1.2.0 include a terminal, but when I try to install any pack with node I get the npm ERR! code EPERM that I usually solve right clicking and running it as administrator. So how I do that in the vscode terminal? There is something like sudo for linux?

[![vscode terminal][1]][1]


  [1]: https://cloud.githubusercontent.com/assets/4368630/15891190/5e101d12-2d6b-11e6-9ef3-77d05bedce01.PNG

Visual studio code terminal, how to run a command with administrator rights?

I am running the exact same code on both windows and mac, with python 3.5 64 bit. 

On windows, it looks like this:

    &gt;&gt;&gt; import numpy as np
    &gt;&gt;&gt; preds = np.zeros((1, 3), dtype=int)
    &gt;&gt;&gt; p = [6802256107, 5017549029, 3745804973]
    &gt;&gt;&gt; preds[0] = p
    Traceback (most recent call last):
      File &quot;&lt;pyshell#13&gt;&quot;, line 1, in &lt;module&gt;
        preds[0] = p
    OverflowError: Python int too large to convert to C long
    
However, this code works fine on my mac. Could anyone help explain why or give a solution for the code on windows? Thanks so much!

&quot;OverflowError: Python int too large to convert to C long&quot; on windows but not mac

I was trying to navigate to my drive location `E:/Study/Codes` in `git bash` in windows. In command prompt in order to change drive I use `E:` It returns an error in `git bash`. 

&gt; bash: E:: command not found.

 How do I change my current directory location from `/c/users` to `E:Study/Codes`

Change drive in git bash for windows

I just installed the latest SDK(10.0.10586.0) and was wondering if I can delete the libraries from the older Windows 10 SDKs(10.0.10240.0 and 10.0.10150.0)?   

Or is there a safe way or a program to do this?

Is it OK to delete older versions of Windows 10 SDK?

I&#39;ve just upgraded the Windows 10 in my laptop to Redstone 1. So I had a test of the Linux subsystem (aka. WSL, LXSS or Bash on Windows). Basically, everything is fine, but there is a problem that the RootFS of WSL is located in the `%LocalAppData%` path (e.g. `C:\Users\xyz\AppData\Local`), which is also the place where my Windows OS located. It consumes a lot of the SSD hard drive space in my laptop and I hope I can move it to my external hard drive. 

There is an another problem. Since the other hard drive partitions are mounted as DriveFS, it does not support some Linux filesystem features like `chmod`, and some of my Linux project build scripts only works in VoIFS, which only located in `/` and `/home`.

So I tried to move the whole WSL RootFS to another hard drive. Firstly I&#39;ve tried to make a NTFS Junction (hard link) for `C:\Users\xyz\AppData\Local\lxss`. I&#39;ve uninstalled the WSL completely and run `mklink` for the RootFS to another hard drive, and when I reinstall the WSL again, **it couldn&#39;t create the new user, and it reports error with code 0x80070003.**

Then I searched around, and I got this: [moving Linux filesystem - issue #449][1]. **It seems that moving and making hard link for WSL RootFS only works before Windows 10 Build 14388, it does not work in the Windows 10 Build 14393 RTM.** The only way is moving the whole `%LocalAppData%` to the external hard drive, but I cannot do that since I&#39;m a laptop user and I can&#39;t bring an external hard drive everywhere!

So I would like to ask that, is there any other ways to move WSL out of my system partition? If I can&#39;t do that, **can I create an extra VoIFS work directory in some other places and compile my stuff?**

Thanks and regards,
Jackson

  [1]: https://github.com/Microsoft/BashOnWindows/issues/449

Move WSL (Bash on Windows) root filesystem to another hard drive?

I am working on a project that needs to connect to an https site. Every time I connect, my code throws exception because the certificate of that site comes from untrusted site.  Is there a way to bypass certificate check in .net core http?

I saw this code from previous version of .NET. I guess I just need something like this.
     
     ServicePointManager.ServerCertificateValidationCallback += (sender, cert, chain, sslPolicyErrors) =&gt; true;

bypass invalid SSL certificate in .net core

I recently added SSL to my website and it can be accessed over https. Now when my java application tries to make requests to my website and read from it with a buffered reader it produces this stack trace 

Im not using a self signed certificate the cert is from Namecheap who uses COMODO SSL as the CA to sign my certificate. im using java 8

    javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
	at sun.security.ssl.Handshaker.activate(Handshaker.java:503)
	at sun.security.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1482)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1351)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)

My code is very basic and simply tries to read the page on my site using a buffered reader 

     private void populateDataList() {
        try {
            URL url = new URL(&quot;https://myURL.com/Data/Data.txt&quot;);
            URLConnection con = url.openConnection();
            con.setRequestProperty(&quot;Connection&quot;, &quot;close&quot;);
            con.setDoInput(true);
            con.setUseCaches(false);

            BufferedReader in = new BufferedReader(new InputStreamReader(con.getInputStream()));
            String line;
            int i = 0;
            while((line = in.readLine()) != null) {
                this.url.add(i, line);
                i++;
            }
        }   catch (Exception e) {
            e.printStackTrace();
        }

    }

Ive tried adding my SSL certificate to the JVM&#39;s Keystore and Ive also even tried to accept every certificate (which defeats the purpose of SSL I know) with this code 

     private void trustCertificate() {
        TrustManager[] trustAllCerts = new TrustManager[] {
                new X509TrustManager() {
                    public java.security.cert.X509Certificate[] getAcceptedIssuers() {
                        return new X509Certificate[0];
                    }
                    public void checkClientTrusted(
                            java.security.cert.X509Certificate[] certs, String authType) {
                    }
                    public void checkServerTrusted(
                            java.security.cert.X509Certificate[] certs, String authType) {
                    }
                }
        };
        try {
            SSLContext sc = SSLContext.getInstance(&quot;TLS&quot;);
            sc.init(null, trustAllCerts, new java.security.SecureRandom());
            HttpsURLConnection.setDefaultSSLSocketFactory(sc.getSocketFactory());
        } catch (GeneralSecurityException e) {
        }
        try {
            URL url = new URL(&quot;https://myURL.com/index.php&quot;);
            URLConnection con = url.openConnection();
            BufferedReader br = new BufferedReader(new InputStreamReader(con.getInputStream()));
            String line;
            while((line = br.readLine()) != null) {
                System.out.println(line);
            }

        } catch (Exception e) {

        }
    }

Im stumped and any help would be much appreciated! 

SSLHandShakeException No Appropriate Protocol

I am just simply trying to add the domain `test.example.com` to the certificate that already exists for `example.com`. How do I add a domain to my existing certificate and replace the old certificate?

I have tried these few commands

    ./letsencrypt-auto certonly --cert-path /etc/letsencrypt/archive/example.com --expand -d test.example.com

    ./letsencrypt-auto certonly -d example.com --expand -d test.example.com

Result: both created a brand new cert in a new folder test.example.com-0001


    ./letsencrypt-auto certonly --renew-by-default  --expand -d test.example.com

Result: error folder test.example.com already exists.




    ./letsencrypt-auto renew --expand -d orange.fidka.com

Result: error, I can only renew if my certificate is expired.
    

Letsencrypt add domain to existing certificate

I have developer server that are used for testing. They have SSL self-signed certificates, which allow us to test the web application over HTTPS, but with prominent warnings that the certificates are not verifiable.

That&#39;s fine, but I have a Service Worker that throws an error with the `navigator.serviceWorker.register`

&gt; SecurityError: Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script.

How do I use a Service Worker with an intranet testing server which has a self-signed certificate?

Can you use a service worker with a self-signed certificate?

I&#39;m working on an app for which the (power)users have to set up their own server (i.e. nginx) to run the backend application. The corresponding domain needs to be configured in the app so it can connect. I&#39;ve been testing primarily on my own phone (sony z3c) and started developing for 5.1. Later I received an update for 6.0 but still maintained a working 5.1 inside the emulator. Not too long ago, I started to work on an AVD with an image for 7.0 and to my suprise it won&#39;t connect to my server, telling me the ssl handshake failed. My nginx configuration is pretty strict, but it works for both 5.1 and 6.0, so .... ?!

Here is what I know:

- I use v24 for support libs, i.e. my compileSdkVersion is 24.
- I use Volley [v1.0.0](https://bintray.com/android/android-utils/com.android.volley.volley).
- I&#39;ve tried the [TLSSocketFactory](https://stackoverflow.com/a/33874126), but it doesn&#39;t change anything. This seems to be used most of the times to prevent SSL3 use for older SDK versions anyway.
- I&#39;ve tried increasing the [timeout](https://stackoverflow.com/questions/32184787/com-android-volley-noconnectionerror-javax-net-ssl-sslhandshakeexception-javax), but it doesn&#39;t change anything.
- I&#39;ve tried using HttpURLConnection directly, but it doesn&#39;t change anything apart from the stack trace (it&#39;s without the volley references, but identical otherwise).

Without the TLSSocketFactory the request are made through a bare request queue, instantiated with ```Volley.newRequestQueue(context)```.

This is what I see in android studio:

    W/System.err: com.android.volley.NoConnectionError: javax.net.ssl.SSLHandshakeException: Connection closed by peer
    W/System.err:     at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:151)
    W/System.err:     at com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
    W/System.err: Caused by: javax.net.ssl.SSLHandshakeException: Connection closed by peer
    W/System.err:     at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
    W/System.err:     at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:357)
    W/System.err:     at com.android.okhttp.Connection.connectTls(Connection.java:235)
    W/System.err:     at com.android.okhttp.Connection.connectSocket(Connection.java:199)
    W/System.err:     at com.android.okhttp.Connection.connect(Connection.java:172)
    W/System.err:     at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:367)
    W/System.err:     at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:130)
    W/System.err:     at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:329)
    W/System.err:     at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:246)
    W/System.err:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:457)
    W/System.err:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:126)
    W/System.err:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:257)
    W/System.err:     at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getOutputStream(DelegatingHttpsURLConnection.java:218)
    W/System.err:     at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java)
    W/System.err:     at com.android.volley.toolbox.HurlStack.addBodyIfExists(HurlStack.java:264)
    W/System.err:     at com.android.volley.toolbox.HurlStack.setConnectionParametersForRequest(HurlStack.java:234)
    W/System.err:     at com.android.volley.toolbox.HurlStack.performRequest(HurlStack.java:107)
    W/System.err:     at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:96)
    W/System.err:   ... 1 more
    W/System.err:   Suppressed: javax.net.ssl.SSLHandshakeException: Handshake failed
    W/System.err:     at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:429)
    W/System.err:       ... 17 more
    W/System.err:   Caused by: javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0x7ffef3748040: Failure in SSL library, usually a protocol error
    W/System.err: error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE (external/boringssl/src/ssl/s3_pkt.c:610 0x7ffeda1d2240:0x00000001)
    W/System.err: error:1000009a:SSL routines:OPENSSL_internal:HANDSHAKE_FAILURE_ON_CLIENT_HELLO (external/boringssl/src/ssl/s3_clnt.c:764 0x7ffee9d2b70a:0x00000000)
    W/System.err:     at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
    W/System.err:     at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:357)
    W/System.err:       ... 17 more

Since it says ```SSLV3_ALERT_HANDSHAKE_FAILURE``` I can only assume it for some reason tries to connect using SSLv3 and fails, but this doesn&#39;t make any sense to me whatsoever. It might be a cipher-issue, but how can I tell what it is trying to use ? I would rather not enable a ciphers on the server, make a connection attempt and repeat.

My nginx site uses a let&#39;s encrypt certificate and has the following configuration:

    ssl_stapling on;
    ssl_stapling_verify on;
    ssl_trusted_certificate /etc/ssl/certs/lets-encrypt-x1-cross-signed.pem;
    ssl_ciphers ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:!aNULL;
    ssl_dhparam /etc/ssl/certs/dhparam.pem;
    ssl_ecdh_curve secp384r1;
    ssl_prefer_server_ciphers on;
    ssl_protocols TLSv1.2;

To test these ciphers I&#39;ve a [script](https://superuser.com/a/224263) and it confirms these ciphers (run on a wheezy vps outside the server&#39;s network):

&lt;pre&gt;
Testing ECDHE-RSA-AES256-GCM-SHA384...YES
Testing ECDHE-ECDSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing SRP-DSS-AES-256-CBC-SHA...NO (sslv3 alert handshake failure)
Testing SRP-RSA-AES-256-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-AES256-SHA...NO (sslv3 alert handshake failure)
Testing SRP-AES-256-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ADH-AES256-SHA256...NO (sslv3 alert handshake failure)
Testing ADH-AES256-SHA...NO (sslv3 alert handshake failure)
Testing ADH-CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES256-SHA384...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing AES256-GCM-SHA384...NO (sslv3 alert handshake failure)
Testing AES256-SHA256...NO (sslv3 alert handshake failure)
Testing AES256-SHA...NO (sslv3 alert handshake failure)
Testing CAMELLIA256-SHA...NO (sslv3 alert handshake failure)
Testing PSK-AES256-CBC-SHA...NO (no ciphers available)
Testing ECDHE-RSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing SRP-DSS-3DES-EDE-CBC-SHA...NO (sslv3 alert handshake failure)
Testing SRP-RSA-3DES-EDE-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EDH-RSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing EDH-DSS-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing SRP-3DES-EDE-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing PSK-3DES-EDE-CBC-SHA...NO (no ciphers available)
Testing ECDHE-RSA-AES128-GCM-SHA256...YES
Testing ECDHE-ECDSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing SRP-DSS-AES-128-CBC-SHA...NO (sslv3 alert handshake failure)
Testing SRP-RSA-AES-128-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-SEED-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-SEED-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-AES128-SHA...NO (sslv3 alert handshake failure)
Testing SRP-AES-128-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ADH-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ADH-AES128-SHA...NO (sslv3 alert handshake failure)
Testing ADH-SEED-SHA...NO (sslv3 alert handshake failure)
Testing ADH-CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES128-SHA256...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-AES128-SHA...NO (sslv3 alert handshake failure)
Testing AES128-GCM-SHA256...NO (sslv3 alert handshake failure)
Testing AES128-SHA256...NO (sslv3 alert handshake failure)
Testing AES128-SHA...NO (sslv3 alert handshake failure)
Testing SEED-SHA...NO (sslv3 alert handshake failure)
Testing CAMELLIA128-SHA...NO (sslv3 alert handshake failure)
Testing PSK-AES128-CBC-SHA...NO (no ciphers available)
Testing ECDHE-RSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-RC4-SHA...NO (sslv3 alert handshake failure)
Testing ADH-RC4-MD5...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-RC4-SHA...NO (sslv3 alert handshake failure)
Testing RC4-SHA...NO (sslv3 alert handshake failure)
Testing RC4-MD5...NO (sslv3 alert handshake failure)
Testing PSK-RC4-SHA...NO (no ciphers available)
Testing EDH-RSA-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EDH-DSS-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-EDH-RSA-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-EDH-DSS-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-ADH-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-RC2-CBC-MD5...NO (sslv3 alert handshake failure)
Testing EXP-ADH-RC4-MD5...NO (sslv3 alert handshake failure)
Testing EXP-RC4-MD5...NO (sslv3 alert handshake failure)
Testing ECDHE-RSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing ECDHE-ECDSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing AECDH-NULL-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-RSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing ECDH-ECDSA-NULL-SHA...NO (sslv3 alert handshake failure)
Testing NULL-SHA256...NO (sslv3 alert handshake failure)
Testing NULL-SHA...NO (sslv3 alert handshake failure)
Testing NULL-MD5...NO (sslv3 alert handshake failure
&lt;/pre&gt;

I *can* open the server-url in the emulator&#39;s browser and get a perfect json response so I know the system itself is capable.

So the question is, why can&#39;t I connect on Android 7 ?

**Update**:

I&#39;ve looked at a captured packet using tcpdump and wireshark and the enabled ciphers are in the ClientHello, so that should not be a problem.

&lt;pre&gt;
Cipher Suites (18 suites)

Cipher Suite: Unknown (0xcca9)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
Cipher Suite: Unknown (0xcca8)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
&lt;/pre&gt;

As you can see ```0xc02f``` and ```0xc030``` match, but the next TLSv1.2 packet says: ```Alert (21), Handshake Failure (40)```.

**Update 2**:

These are the curves from Android 5.1 in the ClientHello:

&lt;pre&gt;
Elliptic curves (25 curves)

Elliptic curve: sect571r1 (0x000e)
Elliptic curve: sect571k1 (0x000d)
Elliptic curve: secp521r1 (0x0019)
Elliptic curve: sect409k1 (0x000b)
Elliptic curve: sect409r1 (0x000c)
Elliptic curve: secp384r1 (0x0018)
Elliptic curve: sect283k1 (0x0009)
Elliptic curve: sect283r1 (0x000a)
Elliptic curve: secp256k1 (0x0016)
Elliptic curve: secp256r1 (0x0017)
Elliptic curve: sect239k1 (0x0008)
Elliptic curve: sect233k1 (0x0006)
Elliptic curve: sect233r1 (0x0007)
Elliptic curve: secp224k1 (0x0014)
Elliptic curve: secp224r1 (0x0015)
Elliptic curve: sect193r1 (0x0004)
Elliptic curve: sect193r2 (0x0005)
Elliptic curve: secp192k1 (0x0012)
Elliptic curve: secp192r1 (0x0013)
Elliptic curve: sect163k1 (0x0001)
Elliptic curve: sect163r1 (0x0002)
Elliptic curve: sect163r2 (0x0003)
Elliptic curve: secp160k1 (0x000f)
Elliptic curve: secp160r1 (0x0010)
Elliptic curve: secp160r2 (0x0011)
&lt;/pre&gt;

In the ServerHello ```secp384r1 (0x0018)``` is returned.

And this is from Android 7:

&lt;pre&gt;
Elliptic curves (1 curve)

Elliptic curve: secp256r1 (0x0017)
&lt;/pre&gt;

Resulting in the Handshake Failure.

Changing the nginx configuration by removing secp384r1 or replacing it with the default (prime256v1) does get it to work. So I guess the question remains: am I able to add elliptic curves ?

The captured data is the same when using the emulator as when using an Android 7.0 device (General Mobile 4G).

**Update 3**:

Small update, but worth mentioning: I got it to work in the emulator using Android 7.1.1 (!). It shows the following data (again, grabbed using tcpdump and viewed using wireshark):

&lt;pre&gt;
Elliptic curves (3 curves)

Elliptic curve: secp256r1 (0x0017)
Elliptic curve: secp384r1 (0x0018)
Elliptic curve: secp512r1 (0x0019)
&lt;/pre&gt;

It shows the same 18 Cipher Suites.


SSLHandshakeException: Handshake failed on Android N/7.0

Upgraded to `Ubuntu 16.04` and facing problem after installing `PHP5`.

**Installed PHP-5 with following:**

    sudo add-apt-repository ppa:ondrej/php
    sudo apt-get update
    sudo apt-get upgrade
    sudo apt-get install php5.5   # for PHP 5.5

Trying to install php-curl but its not working.

    sudo apt-get install php5-curl

&gt; Error: E: Unable to locate package php5-curl



How to install php-curl in Ubuntu 16.04

I use curl to get http headers to find http status code and also return response. I get the http headers with the command

    curl -I http://localhost

To get the response, I use the command 

    curl http://localhost

As soon as use the -I flag, I get only the headers and the response is no longer there. Is there a way to get both the http response and the headers/http status code in in one command?

Curl to return http status code along with the response

I am trying to pull some json data from a remote server using `fromJSON`:

    &gt; server &lt;- &#39;http://111.111.000.00:3000&#39;
    &gt; streams &lt;- fromJSON(paste(server, &#39;/output/streams&#39;, sep=&quot;&quot;), flatten=TRUE)

Result:

    Error: Required package curl not found. 
    Please run: install.packages(&#39;curl&#39;)

So I tried to install it:

    &gt; install.packages(&quot;curl&quot;)
    Installing package into ‘/home/lauxxx/R/x86_64-pc-linux-gnu-library/3.3’
    (as ‘lib’ is unspecified)
    trying URL &#39;https://cran.rstudio.com/src/contrib/curl_2.3.tar.gz&#39;
    Content type &#39;application/x-gzip&#39; length 400460 bytes (391 KB)
    ==================================================
    downloaded 391 KB
    
    * installing *source* package ‘curl’ ...
    ** package ‘curl’ successfully unpacked and MD5 sums checked
    Using PKG_CFLAGS=
    Using PKG_LIBS=-lcurl
    ------------------------- ANTICONF ERROR ---------------------------
    Configuration failed because libcurl was not found. Try installing:
     * deb: libcurl4-openssl-dev (Debian, Ubuntu, etc)
     * rpm: libcurl-devel (Fedora, CentOS, RHEL)
     * csw: libcurl_dev (Solaris)
    If libcurl is already installed, check that &#39;pkg-config&#39; is in your
    PATH and PKG_CONFIG_PATH contains a libcurl.pc file. If pkg-config
    is unavailable you can set INCLUDE_DIR and LIB_DIR manually via:
    R CMD INSTALL --configure-vars=&#39;INCLUDE_DIR=... LIB_DIR=...&#39;
    --------------------------------------------------------------------
    ERROR: configuration failed for package ‘curl’
    * removing ‘/home/lauxxx/R/x86_64-pc-linux-gnu-library/3.3/curl’
    Warning in install.packages :
      installation of package ‘curl’ had non-zero exit status
    
    The downloaded source packages are in
    	‘/tmp/RtmpdoavNf/downloaded_packages’

Then I tried to install `libcurl4-openssl-dev`:

    &gt; install.packages(&quot;libcurl4-openssl-dev&quot;)
    Installing package into ‘/home/lau/R/x86_64-pc-linux-gnu-library/3.3’
    (as ‘lib’ is unspecified)
    Warning in install.packages :
      package ‘libcurl4-openssl-dev’ is not available (for R version 3.3.1)

Why? What is going wrong? How can I fix it?

It was ok when I was on Xubuntu 16.04. But now I am on Kubuntu 16.10.

Any ideas?

Configuration failed because libcurl was not found

I am running an ASP.NET Core 1.1 Web API in a Docker 1.13.1 container on Ubuntu 14.04.

When the code attempts to retrieve some data from an HTTPS server, I get this certificate authentication error:

	 An error occurred while sending the request. ---&gt; System.Net.Http.CurlException: Peer certificate cannot be authenticated with given CA certificates
	   at System.Net.Http.CurlHandler.ThrowIfCURLEError(CURLcode error)
	   at System.Net.Http.CurlHandler.MultiAgent.FinishRequest(StrongToWeakReference`1 easyWrapper, CURLcode messageResult)

The HTTPS server is internal with certificate signed by our corporate CA, so am aware that I may need to register the internal CA.

Everything I&#39;ve found so far about this error and Docker talks to getting docker itself running, connecting to repos etc.  My Docker is working fine, and the Web API runs on the Ubuntu server outside of the container without a problem.

1) Do I need to add a CA root certificate inside a docker image?

2) If so, how do I do it?

3) If not, how do I fix this? 

How do I add a CA root certificate inside a docker image?

I have a script I run to deploy 2 web services and a front-end application. The script calls a method that checks to see if the 2 back-end services are up and running. If so, deem the deploy successful, otherwise revert.

The 2 services sometimes take longer than the front-end to start up. Currently I put in a sleep call to delay the web service check. This allows them time to start up.

I want to remove this sleep and add in a retry mechanism so that if a service is down, just retry the check repeatedly until I get a response.

Tp check if the device is up, I use curl. I&#39;ve read that curl has a retry mechanism but I&#39;ve never used it.

Have any of you solved this problem before? I want to understand the things I must consider when solving it, e.g. do I retry until i get a HTTP 200 from my service?

Anyone any suggestions how I&#39;d test this? I&#39;d need to find a service that was down.

EDIT: I see that -retry only reacts to transient errors &#39;Transient error means either: a timeout, an FTP 4xx response code or an HTTP 5xx response code&#39;. My service can return a 404 therefore curl&#39;s retry is not my solution.

Curl retry mechanism

https://github.com/angular/angular-cli#proxy-to-backend here is an instruction how to do proxying to backend. I did everything step by step and still requests aren&#39;t proxied.

8080 - my Express backend
4200 - my Angular2 frontend

In Angular2 project I have file ```proxy.conf.json``` with content like this:

    {
      &quot;/api&quot;: {
        &quot;target&quot;: &quot;http://localhost:8080&quot;,
        &quot;secure&quot;: false
      }
    }

In Angular2 package.json I changed ```start``` procedure to ```&quot;start&quot;: &quot;ng serve --proxy-config proxy.conf.json&quot;```

When I type inside commander ```npm start``` then at the start I can see ```Proxy created: /api -&gt; http://localhost:8080```. Well, so far is good I guess.

I&#39;m trying to send a request (Angular2)

      constructor(private http: Http) {
        this.getAnswer();
      }
    
      getAnswer(): any {
        return this.http.get(&quot;/api/hello&quot;)
          .subscribe(response =&gt; {
            console.log(response);
          })
      }

I&#39;m getting an error that ```http://localhost:4200/api/hello 404 (Not Found)```. As we can see, nothing has been proxied. Why? Did I do something wrong?

To be clear. When I go manually to ```http://localhost:8080/hello```, all works fine. There is nothing to look for in backend side.

Angular-CLI proxy to backend doesn&#39;t work

I have this code in js bin: 



    var validator = {
      set (target, key, value) {
        console.log(target);
        console.log(key);
        console.log(value);
        if(isObject(target[key])){
          
        }
        return true
      }
    }
    
    
    var person = {
          firstName: &quot;alfred&quot;,
          lastName: &quot;john&quot;,
          inner: {
            salary: 8250,
            Proffesion: &quot;.NET Developer&quot;
          }
    }
    var proxy = new Proxy(person, validator)
    proxy.inner.salary = &#39;foo&#39;




if i do `proxy.inner.salary = 555;` it does not work.

However if i do `proxy.firstName = &quot;Anne&quot;`, then it works great.

I do not understand why it does not work Recursively.

http://jsbin.com/dinerotiwe/edit?html,js,console

How to use javascript proxy for nested objects

I&#180;m performing some WPO tasks, so PageSpeed suggested me to leverage browser caching. I have improved it successfully for some static files in my Nginx server, however my image files stored in Amazon S3 server are still missing. 

I have read an approach regarding update each file in S3 to include some header metatags (Expires and Cache-Control). I think this is not a good approach. I have thousands of files, so this is not feasible for me.

I think a most convenient approach is to configure my Nginx 1.6.0 server to proxy the S3 files. I have read about this, but I&#180;m not skilled at all on server config, so I got a couple examples from these sites: https://gist.github.com/benjaminbarbe/1961db5ffbaad57eff12 


I added this location code inside my server block in my nginx config file:

    #inside server block
    location /mybucket.s3.amazonaws.com/ {
		    		    
		 
		    proxy_http_version     1.1;
		    proxy_set_header       Host mybucket.s3.amazonaws.com;
		    proxy_set_header       Authorization &#39;&#39;;
		    proxy_hide_header      x-amz-id-2;
		    proxy_hide_header      x-amz-request-id;
		    proxy_hide_header      Set-Cookie;
		    proxy_ignore_headers   &quot;Set-Cookie&quot;;
		    proxy_buffering        off;
		    proxy_intercept_errors on;		
		    proxy_pass             http://mybucket.s3.amazonaws.com;
		  }

For sure, this is not working for me. No header is included in my requests. So, first I think the requests are not matching the locations.

    Accept-Ranges:bytes
    Content-Length:90810
    Content-Type:image/jpeg
    Date:Fri, 23 Jun 2017 04:53:56 GMT
    ETag:&quot;4fd0be549fbcaf9b47c18a15146cdf16&quot;
    Last-Modified:Tue, 09 Jun 2015 09:47:13 GMT
    Server:AmazonS3
    x-amz-id-2:cKsq1qRra74DqVsTewh3P3sgzVUoPR8aAT2NFCuwA+JjCdDZfk7/7x/C0WPjBa51GEb4C8LyAIc=
    x-amz-request-id:94EADB4EDD3DE1C1

 

Nginx proxy Amazon S3 resources

I am in a corporate env so I have to use a proxy to reach servers. This works well in postman and in browsers. What I can&#39;t reach is localhost in postman but I can reach localhost in the browser. 

I am running Postman for Linux Version 6.0.9. I have tried reaching localhost:9082/rest/myapi.... and 127.0.0.1:9082/rest/myapi with both global proxy and system proxy turned on and with either turned on and with non turned on. In all cases I am not able to reach localhost.

What I get as an response is an error page from the proxy server! Someway the call gets out on the network instead of being kept on my machine.

The postman console:

My request headers are:

    Cache-Control →no-cache
    Connection →Keep-Alive
    Content-Length →986
    Content-Type →text/html; charset=utf-8
    Pragma →no-cache
    Proxy-Connection →Keep-Alive

My response headers are:

    cache-control:&quot;no-cache&quot;
    pragma:&quot;no-cache&quot;
    content-type:&quot;text/html; charset=utf-8&quot;
    proxy-connection:&quot;Keep-Alive&quot;
    connection:&quot;Keep-Alive&quot;
    content-length:&quot;986&quot;

My response body is an html page.

How can I make a call to `localhost` work with postman?

Postman can&#39;t reach localhost

I added proxy in package.json and it worked great, but after npm run build the CORS issue has resurfaced again, does anyone know how to deal with CORS issue after npm run build in React.

I have tried to add headers in axios request using various methods. However, I failed to add &#39;Access-Control-Allow-Origin&#39;:&#39;*&#39; in axios request. My code is as follwing:

package.json
    
      &quot;proxy&quot;: {
          &quot;*&quot;:{ &quot;target&quot; : &quot;http://myurl&quot;}
       } 

GetData.js

      axios.defaults.baseURL = &#39;http://myurl&#39;;
      axios.defaults.headers.post[&#39;Content-Type&#39;] =&#39;application/json;charset=utf-8&#39;;
      axios.defaults.headers.post[&#39;Access-Control-Allow-Origin&#39;] = &#39;*&#39;;
      axios.get(serviceUrl, onSuccess, onFailure)
      .then(resp =&gt; { 
            let result = resp.data;
            onSuccess(result);
      })
      .catch(error =&gt; {
            if(onFailure) {
                return onFailure(error);
            }
      })
     }

Note: It has enabled from server side, it is still not working.Currently, I can&#39;t change code from server side, My work is limited to client side only.


Content Type	Original Author	Original Content on Stackoverflow
Question	BSalita	View Question on Stackoverflow
Solution 1 - Windows	BSalita	View Answer on Stackoverflow

Why Doesn't Fiddler Show Curl Traffic?

Windows Problem Overview

Windows Solutions

Solution 1 - Windows

Error when converting VmWare virtual disk to HyperV

Extract Month and Year From Date in R

Attributions