Hi Paul, Thanks for the data. This is very strange. If I’m reading this correctly, the monitor never saw the request for apache-flex-sdk-installer-config.xml. The GET /track-installer is where we report the failure to our analytics.
Do you have some sort of firewall that could be blocking the installer but not the browser? Thanks, -Alex On 2/3/15, 12:01 AM, "Paul Hastings" <paul.hasti...@gmail.com> wrote: >On 2/3/2015 2:16 PM, Alex Harui wrote: >> I think so. The log showed it failed getting to that file. I assume >>the >> checkboxes did not show and the log showed the same file on each run? > >yup. > > >looking thru the capture w/HTTP "view" i see (where ONGKHARAK is my dev >w/s & >columns are: protocol,frame,time delta,process,source,dest,http summary, >http >reasons): > >HTTP 9600 0.0025229 Apache Flex SDK Installer.exe ONGKHARAK > 192.87.106.229 >Request, GET /installer/sdk-installer-config-4.0.xml > >HTTP 9607 0.7633080 Apache Flex SDK >Installer.exe 192.87.106.229 ONGKHARAK >Response, HTTP/1.1, Status: Ok, URL: >/installer/sdk-installer-config-4.0.xml OK > > >then the wheels fall off here (though its outbound)??? > >HTTP 9844 0.0040899 Apache Flex SDK Installer.exe ONGKHARAK > 192.87.106.229 >Request, GET /track-installer.html, >Query:failure=true&label=Apache%20Flex%20SDK%204.14.0&version=4.14.0&os=wi >ndowsUnable%20to%20load%20https://www.apache.org/dist/flex/4.14.0/binaries >/apache-flex-sdk-installer-config.xml > > >HTTP 9855 0.8554907 Apache Flex SDK >Installer.exe 192.87.106.229 ONGKHARAK >Response, HTTP/1.1, Status: Ok, URL: /track-installer.html OK > >followed by a bunch of CSS, JS, & image file gets. > >i noticed that the protocols swap back & forth between HTTP & HTTPS, is >this new? > >anything else i should look for? do you want the capture files? >
