Angular 2 application 404 error when refresh from browser - angular2-routing

I just checked a site developed in angular 2 (https://thepoolcover.co.uk/), When i hard refresh this application internal pages its display appropriate page and related content but in my angular 2 app when i hard refresh any internal pages it shows 404 error. Can you please share the suggestions it would be great help for me

Related

Zoom Web SDK integration issue in asp.net

I am working on video conference with Zoom Web SDK 1.9 in asp.net(C#) web application, and it is working as expected.
But as soon as I join the zoom meeting and try to refresh the page or navigate to other page via menu, it is automatically logged out from the web application and redirect to login page. Without joining zoom meeting all pages of web application are working fine, with no logout issue.
Now I have to re-login into the web application to visit other page. If any one having any idea on how to overcome with this problem please suggest.

Looking for Server Side Rendering using VUEJS having ASPX page and site hosting on IIS7

We have our existing pages in ASPX and site is hosted on IIS7 server.
We are looking for revamping/design the pages in VUEJS 2.0.
We are able to get VueJS code integrated with existing ASPX pages by getting build.js generated (production) and referring the same on ASPX page and page will be having the Target element. This all is client side rendering.
Now, we want the same in SSR. That mean to be complete HTML code rendered on the page before being served to the client (browser).
This clearly indicates we need to setup NodeServer, which can be called up by ASP.NET to get the VUEJS code rendered and added on ASPX page before it's being served to the Client (Browser). Please correct me If I am wrong. Here we are looking for a dynamic webages (Not the static one with prerendering or static generation)
We have started looking up for NUXT.JS as one of the options. But this is recommended to be used for the apps hosted for NodeServer.
ref:https://github.com/MarkPieszak/aspnetcore-Vue-starter/issues/67
1: https://github.com/MarkPieszak/aspnetcore-Vue-starter/issues/67
Other big challenge going with Nuxt is, they are likely launching Nuxt2.js version, which may or may not have breaking changes. https://medium.com/nuxt/nuxt-2-is-coming-oh-yeah-212c1a9e1a67
Next option is to looking for following:
https://github.com/MarkPieszak/aspnetcore-Vue-starter
https://github.com/vuejs/vue-hackernews-2.0
http://mgyongyosi.com/2016/Vuejs-server-side-rendering-with-aspnet-core/
Above links mentions using ASP.net core API Microsoft.AspNetCore.SpaServices.Webpack.
I believe you must have faced this situation and reached to an optimal solution. I am looking for suggestions from veterans have achieved the same, what path to be followed?
IF this can be achieved at all? and what are the challenges I should look forward?
Thanks

App migrated to .net 4, NewRelic shows double requests and time in System.Web.DefaultHttpHandler

We have just migrated an app from .Net 2 to .Net 4 (without major code changes); the app uses a custom HttpModule to serve extensionless URLs (based on a 404 page - request comes in, hits our custom 404 page, goes through the module and gets transferred to the correct page behind the scenes).
Everything is working well post-migration, but NewRelic is showing a very high number of requests per minute (we know it's not right, because we can monitor current requests on the firewall or load balancer) and showing a lot of time spent in /System.Web.DefaultHttpHandler.
Has anyone seen this before? I suspect it could be ASP .Net trying to handle the extensionless URL for us, but I'm not sure how to prevent this - I'm just working to get an enviroment where I can do a bit of testing, but if anyone has any suggestions I'd love to hear them!
Thanks
Sam
Just in case anyone else comes across this - it was just a matter of removing the ASP .Net 4 extensionless URL handler via web.config, as it was trying to also process the request at the same time as our 404 handler.

Why a 404 on every available page on a Web Site project?

I've just opened a Web Site project found on my predecessor's machine and - I hate the things and don't ever work with them - I get a 404 on every link I click, while the page is definitely present. If I directly view the individual page in the browser, that page works fine, except for any links on it to other pages.
It's like the built-in dev web server isn't operating and interpreting URL requests, but I have no idea where to look to clear this up.
USING IIS: If I create and deploy this site under IIS, everything seems to work normally.
MY MAIN QUESTION IS: Why do pages get not get served on this site and do get served on similar sites, under debugging a Web Site project on VS2012. It is not how to solve the problem by deploying to IIS.

ScriptResource.axd 404 error ONLY on subdomains

I have setup my website (ASP.NET 4.0) with AJAX, running with no problems at all.
When I test my website locally and on my main top level domain, there are no problems.
When I'm on a subdomain page, AJAX client side framework fails to load. I observed the problem deeply and found that whenever I'm on a subdomain page, WebResource.axd DOES load but ScriptResource.axd DOESN'T load (returns 404 Not Found error). I think I should modify some entries at web.config file, but I have no idea on what to do?
If you want to see the problem live, go to www.123tiendas.com/subdominios/articulo/default.aspx?id=2020 and there's no problem. Go to www.articulo.123tiendas.com/?id=2020 and you'll see the problem. (use any web developer tools to see what is returned)
GET http://articulo.123tiendas.com/ScriptResource.axd?d=BHVdt7ZKRNgWkcmIzZPX-cQ…NHSxpLPXcqbJyg46pdNsVlEnaL_JpR-IQ0IdhPXwT575CanbqzCN8vtDLDFF9A2&t=48e38e19 404 (Not Found) articulo.123tiendas.com:119

Resources