I have an ASP.NET Core 3.1 Blazor Server-Side Application.
Recently a user has complained, that it does not work with the TOR Browser.
So I tried it out and had to find out, it works in only ~50% of all cases.
Every time I tried, I requested a new circuit for the request.
When it worked, everything was fine and even the speed was not that bad.
But if not, first, the tab is loading the source, showing the favicon and then nothing happens for a while.
Sometimes, if you are patient enough it looks like the first render happens, but the second and so on for all the async operations never happens.
Is there a difference between the TOR nodes, that prevents Blazor pages from working properly?
Tor by default blocks javascript, which blazor signalR is based on, so it can't effectively communicate with the server, disable noscript.
Also k
Related
I'm working on an ASP.Net MVC application, running on .Net Framework 4.6.2. The application is currently deployed to a server with IIS 10.
Everything was working fine, until recently, we added some video (mp4) files into the website. Now, whenever staffs from our company browses the website and open up a video, and browse away to another page on the website before the video is completely played, the website no longer loads correctly for that user's browser.
If the video is fully streamed to the browser, then everything works as expected afterwards.
The videos are served with the HTML5 video tag, directly pointing to a physical file on the server, without any other JavaScript library:
<video src="video.mp4" controls controlslist="nodownload" disablepictureinpicture oncontextmenu="return false;" />
Note that the same behaviour happens if we directly browse to the video (browsing the src URL directly).
From IIS, I found that once a video begins to stream to a browser, if the video is not fully streamed before the user browse away, in subsequent requests there will always be a few static content files that will be stuck in SendResponse state. This causes the browser to be unable to render the page normally, giving the impression that the page would not load.
These static content files are all served with Bundling feature in ASP.Net MVC. Note that not all bundles are not able to be loaded, only some, and those are the bigger bundles of the bunch, but not necessarily the largest. Browser will eventually receive an ERR_HTTP2_PROTOCOL_ERROR for each of those static content bundle after a while, in which the items in SendResponse state on the IIS server will go away.
Strangely, incognito mode and non-incognito mode does not seem to affect one another: if user opens up a video and no longer be able to browse any page on the website in incognito mode, they can still browse the site just fine in non-incognito mode, until they browse to a video in the non-incognito mode.
The same behaviour applies to both Chrome and MS Edge in all the PCs we've tested in our company.
However, the same does not occur to our mobile devices, or our own devices at home.
Failed Request Tracing shows no error. Everything is returning code 200. Filtering the trace to code 400 and above tracked nothing.
I'm at a loss what other methods should I use to continue troubleshooting. Any pointer is greatly appreciated.
After some investigations and trial and errors, it was finally found that the culprit is the antivirus software. A ticket was submitted to the antivirus software company, and they acknowledged that it was their issue and released a hotfix.
Applying the hotfix resolved the problem.
EDIT This issue seems to only affect Chrome and Safari on my Macbook Pro. I can't replicate this issue on other computers and browsers. I thought it might have been malware or virus, so I reformatted my Macbook. Didn't fix the issue All of a sudden, I am running into this issue when developing on my local server as well with MAMP. Assets are missing everywhere and some pages fail to load all together
I've noticed recently when I refresh my Vue SPA with the cache disabled, the page tends to look messed up with missing images/resources.
When I check the console, I see a lot of ERR_CONNECTION_REFUSED for resources that are definitely there. If I refresh the page, the errors go away. It tends to happen after I clear cache and load up the webpage for the first time, or if I disable cache in the developer console.
It turns out there had recently been a DDos attack against my IP address so my hosting service forced rate limit connections to my IP address. So if you ever run into the same issues, check with your hosting company first.
We have a very complicated page with a bunch of partial refreshes going on getting data from several sources and utilizing DOJO and jQuery . Everything works as it should with no problem.
However, when the page is opened multiple times in the same browser on different tabs its seems to lose its session somehow. The partial refreshes don't work anymore and it keeps executing the before and afterPageLoad.
Everything client-side still works, but any calls to the server end up doing nothing.
This happens more when we duplicate the page very fast, if the page is allowed to load fully, the problem seems less frequent.
Telling the browser not to cache seems to make it worse, so it probably has to do with too much traffic.
The pages does use a lot of viewScopes to store data, but no sessionScopes.
Any tips where to look would be appreciated.
Are you losing viewScopes or the whole session? (For an application that requires authentication, you would be prompted to authenticate again when fully refreshing the page. It doesn't sound like that's happening, but I'm not certain.)
Xsp Properties has a setting to determine how many pages to store either in memory or to disk for each page for the current session. Because the current session means the browser session, you might be opening so many pages it dumps the page, so will also dump the viewScope for the earliest tabs. Even if it's the same URL, it will treat it as a separate page if it's a different tab. The number of pages kept is stored on the persistence tab of Xsp Properties. I can't remember what the default is, but 16 rings a bell. It should be documented in XPages Portable Command Guide and possibly Mastering Xpages Second Edition.
It seems it was the page persistence after all. I changed it to 40 and this time I restarted the HTTP task (neglected that the last time).
I can now load other pages without any problems.
Now if I load 40 pages fast, reloading before the page has finished loading, the first one stops responding. If I load it 'normally' 40 times everything works as it should.
seems like the server can't handle the quick reloads.
I had a strange issue from one of my customers this morning, who use my web application. Apparently they are getting "ads" within the browser window when using my application.
I do not put ads in at all. It a straight forward asp.net web application.
What I believe is happening in this case is that the end user has some malware on their pc which "hops" onto their browser session to display their "wares". It could happen to any website they are perusing I guess. I recommended they scan their pc with Malwarebytes.
Is this something that is under the control of the end user, or are there things web application developers can do to prevent this happening. Also some pointers as to how these "ad browser hijackers" work would be good.
Thanks.
I have a massive GWT project with using of spring framework. It's running on Jetty.
When I'm starting this web application - web browser goes to state 'Not Responding' for 10-15 second.
It's very odd, because I can't imagine reason why browser can hang.
Does any one know why such odd behaviour can occur ? Some calculations of javascript ?
It seems that projects starts in in GWT debug mode, and when it's starting GWT actually validates and prepares java code for debugging. In that time browser is in 'hanged up' state.