aspnetcore icon indicating copy to clipboard operation
aspnetcore copied to clipboard

Blazor WASM net::ERR_HTTP2_PROTOCOL_ERROR

Open dajma00 opened this issue 3 years ago • 10 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Describe the bug

I have a Blazor wasm site: https://ims.kfacon.com. When I load it first time, I get this error in console: net::ERR_HTTP2_PROTOCOL_ERROR on several files.

However, when I refresh the same browser, everything runs smooth and site loads.

Expected Behavior

Site should load without the net::ERR_HTTP2_PROTOCOL_ERROR.

Steps To Reproduce

Open Edge browser and navigate to https://ims.kfacon.com If this is the first time, you will get the error. If you will refresh, the error will go away. If you will open in InPrivate windows, you will see the error again.

The behavior is consistent in Edge and Chrome. It does not occur in Firefox.

Exceptions (if any)

Does not happen in Firefox.

.NET Version

.NET 7

Anything else?

No response

dajma00 avatar Nov 21 '22 05:11 dajma00

@dajma00 thanks for contacting us.

I have a Blazor wasm site: https://ims.kfacon.com. When I load it first time, I get this error in console: net::ERR_HTTP2_PROTOCOL_ERROR on several files.

This seems like some type of issue with your network. Can you give us more details about your deployment? As well as any other software that you might have between your machine and the server? (Enterprise proxy, web application firewall, etc.)

javiercn avatar Nov 21 '22 13:11 javiercn

Can you capture a decrypted wireshark trace?

Tratcher avatar Nov 21 '22 15:11 Tratcher

Hi @dajma00. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

ghost avatar Nov 21 '22 15:11 ghost

@dajma00 thanks for contacting us.

I have a Blazor wasm site: https://ims.kfacon.com. When I load it first time, I get this error in console: net::ERR_HTTP2_PROTOCOL_ERROR on several files.

This seems like some type of issue with your network. Can you give us more details about your deployment? As well as any other software that you might have between your machine and the server? (Enterprise proxy, web application firewall, etc.)

The site is hosted on Digital Ocean and is served via Nginx server. There is no proxy, firewall etc. between the client and the site. You can experience yourself by clicking on the site link. I need to dig further to get a Wireshark trace.

dajma00 avatar Nov 21 '22 18:11 dajma00

Can you capture a decrypted wireshark trace?

Where do you want me to load the trace?

dajma00 avatar Nov 22 '22 06:11 dajma00

@dajma00 can you try to share the compressed trace here as an attachment in a comment?

mkArtakMSFT avatar Nov 22 '22 17:11 mkArtakMSFT

Hi @dajma00. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

ghost avatar Nov 22 '22 17:11 ghost

Trace.

@dajma00 can you try to share the compressed trace here as an attachment in a comment?

Trace.zip

dajma00 avatar Nov 23 '22 03:11 dajma00

@dajma00 you'll also need to include the keys file: https://resources.infosecinstitute.com/topic/decrypting-ssl-tls-traffic-with-wireshark/

Tratcher avatar Nov 23 '22 21:11 Tratcher

Hi @dajma00. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

ghost avatar Nov 24 '22 13:11 ghost

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

ghost avatar Nov 28 '22 14:11 ghost