It seems to be related to some Chrome extension which is blocking the request. To debug, you can try incognito mode or --disable-extensions
option from command line.
Another debug trick is shared on "CAUTION: provisional headers are shown" in Chrome debugger:
The way I found about the extension that was blocking my resource was through the chrome://net-internals tool in Chrome. Just type that in the address bar and hit enter. Then open the page that is showing problems. Then go back to net-internals, click on events (###) and use the textfield to find the event related to your resource (use parts of the URL). Finally, click on it and see if the info shown tells you something.