HTTP Header: Timing-Allow-Origin: *

-
<origin>
Specifies a URI that may see the timing resources. You can specify multiple origins, separated by commas.

Comments

Post a Comment

Popular posts from this blog

On Boarding Post

-
Welcome on board guys, I am Shubham . I am a web developer and software engineer currently living in Delhi, India. My interests range from technology to entrepreneurship. I am also interested in running, fitness, and programming. I have more than 3 years of experience in website and mobile applications development. I will be sharing all the solutions to problems that I will face in my daily life personal as well professional. Hang a minute ... personal does not include my girlfriend's talks, just kidding guys. So I hope I will be helping my audience with my experience.  
Read more

How to publish an Node application on Ubuntu.

-
Image
Do you have a dream of seeing your nodeJS application running on a live server?   But all such dreams ended up in a nightmare because you don't know anything about how to use a remote machine? And the dream remains a dream throughout your lifetime. If so then I have my empathy for you because I had been sharing the same nightmare a few days ago ever since when a friend of mine made this simple and made me took a step ahead.  Let me make it  Prerequisites: Make sure you have a running remote machine in Ubuntu14.04, say EC2 instance. If you don't know how to set up a remote machine I promise I will help you up in my upcoming posts. You have an established connection to the remote machine. So that you can access your remote machine. You can use any client say Putty or directly the ssh command. Will surely post about this well. Here are some very simple bullets points to set up a node application: After you successfully connected to the remot...
Read more

Timing tab of chrome dev tools

-
Timing breakdown phases explained Here's more information about each of the phases you may see in the Timing tab: Queueing (no-color, transparent, white ) . The browser queues requests when: The request was postponed by the rendering engine because it's considered lower priority than critical resources (such as scripts/styles). This often happens with images. The request was put on hold to wait for an unavailable TCP socket that's about to free up. The request was put on hold because the browser only allows  six TCP connections  per origin on HTTP 1. Time spent making disk cache entries (typically very quick.) Stalled/Blocking (grey) . Time the request spent waiting before it could be sent. It can be waiting for any of the reasons described for Queueing. Additionally, this time is inclusive of any time spent in proxy negotiation. Proxy Negotiation (grey): Time spent negotiating with a  proxy server  connection. DNS Lookup (Dark green) . Time spent p...
Read more