HTTP2 Protocol Error while loading the website - google-chrome

I am facing an issue while loading the angular web app after any deployment and getting error like ERR_HTTP2_PROTOCOL_ERROR. I am still confused about why this issue is coming again and again. Can anyone please help me with this issue.

Size of the client js file which gets auto-generated while building the angular web gets above 5MB size this error usually comes so if anyone facing the same error either optimize the code to bring down the size or manually minify the js file.

Related

Swagger UI Not Loading Sometimes

I'm using latest version of Swagger in my ASPNetCore 3.1 project and debugging on latest version of Chrome. When I try to enter swagger page it sometimes not loading and i see an empty page. It looks like totally random. It solves after I refresh the page.
I saw these errors on console.
GET https://localhost:44389/swagger/swagger-ui-bundle.js net::ERR_HTTP2_PROTOCOL_ERROR
index.html:95 Uncaught ReferenceError: SwaggerUIBundle is not defined
at window.onload (index.html:95)
File in the error is random. Its sometimes a js file, sometimes a .css file. It changes.
If I publish this project on IIS and disable Http/2 support I never encounter this error.
Why?
You can try the following:
1.Check if all your controller methods have [http] tag. If they all do and still doesn't work go to step 2
2.In your configure function to ensure that you have app.UseStaticFiles(); If it still doesn't work go to step 3
3.Uninstall and reinstall swagger. If it doesn't work go to step 4 (Core Only)
4.If you are using Core Install Microsoft.AspNetCore.StaticFiles and reference it in your project.
I encountered the same problem, SwaggerUIBundle is not defined, and the problem is not on the web app that I'm developing but on my network. The problem was resolved after I switch to another network.

Puppeteer avoid akamai detection

I am trying to scrape a page protected by akamai. There used to be no problems but since a couple of days i am having some troubles.
To scrape the site i am using the latest version of puppeteer, with puppeteer extra and steath.
I have found out that it blockes me from the first connection, so the problem is caused by browser info.
I got the parameters tested on the following site to be nominal. https://bot.sannysoft.com/ still i am getting blocked. Any ideas?
I will upload the blocked .har file shortly.

Getting exception "Unknown Error" after bundling the application(exe)

We are using the evaluation version of JXBrowser for some charting application. We wanted to showcase a demo to our client just to check the overall performance of charts with JXBrowser. But we encountered some unexpected issue while we were trying to build an "EXE".
The issue:
We created a build and the passed the URL from the classpath(webView.getBrowser().loadURL(getClass().getResource("/chartiq/stx-advanced.html").toExternalForm());); the build successfully generated and if we run the build we are getting exception "Unknown Error" but its working fine in the IDE(Eclipse).
Afterwards, we tried to host the html pages at some server and we were able to get the html rendered in the application.
Question:
1. Is the aforementioned issue related to evaluation version?
2. If above question is not the case, is there any fix for that? As we have crawled the web and find nothing related to this.
For the reference I attached the screen shot showing the full exception stacktrace.
Any help will be appreciated.
Thanks,
Nikhil
The reason of this issue is that JxBrowser doesn't support loading resources from JAR files. Chromium engine used in JxBrowser cannot load the /chartiq/stx-advanced.html file located inside JAR archive. You need to extract the file and load the extracted file.
FYI: we have already started working on the functionality that allows loading HTML files and other resources from JAR archives. An updated build with this functionality will be available in December.

Chrome HTTP2.0 throws SPDY PROTOCOL ERROR

I'm using Windows 10 Technical preview. I know it's not yet tweeked out to full usage, but here is my problem.
On local IIS I'm developing my web app. It loads most of the data via ASP.NET MVC API. After the upgrade to Windows 10 I started to get
net::ERR_SPDY_PROTOCOL_ERROR
for all AJAX calls to API. The HTML page loads normally, but the dynamic loading of data content fails. I managed to figure it out by starting Chrome with parameters
--use-spdy=off --use-system-ssl
Strange thing is that on the first start I always get this error and have to restart Chrome. Other browsers fail too, but not with specific error. For the transfer there is used HTTP2.0 protocol, which is based on SPDY protocol.
Do I have to turn something off in IIS?
Edit:
Seems like an IIS problem with HTTP2.0. When trying to enter the site from Windows 8.1 I get the same error.
Most people’s reaction to this error would be to reload the web page. We would actually recommend this as a first response. Sometimes this even does work.
Interesting Factoid: SPDY actually stands for “speedy” and is used to reduce a web pages’ load time
If reloading the web pages does not remove the error, then you should close down Google Chrome and restart it. This alone will not really solve the problem because you will need to clear the cache as soon as you restart the browser.
or in cmd clear dns using this command ipconfig/flushdns

Customize Chromium/Google Chrome error pages

How can I customize the error pages Google Chrome/Chromium displays when there is a networking error (e.g. Error 137 net::ERR_NAME_RESOLUTION_FAILED)
I'm talking about these kinds of pages: http://i41.tinypic.com/29qm8v6.png
They don't seem to be stored anywhere on the file system. Can the errors that make them display be trapped using an extension?
Thanks for any advice.
No, trapping is not possible, and the HTML for the error pages gets built at runtime from compiled resources. See http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/localized_error.cc?view=markup for the code that builds these error pages.
No :(
Correct link at this moment:
https://chromium.googlesource.com/chromium/chromium/+/master/chrome/renderer/localized_error.cc