Internet Information Services
Microsoft web server software.
1,627 questions
I enabled Web Socketing on my IIS and now old ASPX page get error 404, what can I do to fix that?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 11%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EES%3C/text%3E%3C/svg%3E)
Ethan Souders
0
Reputation points
I was building a server side .NET application for my company. I enabled web socketing, which fixed my blazer webserver, however the old ASPX web file are no longer working.
Any ideas on how I can fix this?
{count} votes
-
AgaveJoe 27,421 Reputation points2024-05-30T16:09:43.9+00:00 Web sockets and aspx applications use different protocols I don't see how enabling web sockets would cause existing aspx applications to return a 404. Are you sure you did not turn something off when adding the web socket feature?
Regardless, you'll need troubleshoot. What are the URLs that cause a 404? Is this only happening to certain pages or is it a sitewide issue? How are the IIS application configured? Are the ASP.NET Framework web apps in separate IIS applications? Is the Blazor application in a separate application with its own app pool?
-
Ethan Souders 0 Reputation points
2024-05-30T17:08:01.48+00:00 Thank you very much for the reply.
Checking out the application pool fixed the issue.
I switched the main application .NET CLR to be v4.0.
After that everything worked.
Sign in to comment