Develop Reference

Why do i get a "404 not found" error on IE(not Chrome) in node.js express? and how to solve?

I'm making web server with node.js and express module.
So, I installed node.js, express and express-generator.
And I completed a prototype web server for my project yesterday.
But, when I tested my prototype, I have a strong question.
In Chrome, I could connect for URL like '127.0.0.1:3000'
or '172.30.5.164:3000'(this is my intranet ip address).
But!!
In Explorer, I could't connect!!
So, I tried to find the way.
I solved the 127.0.0.1:3000 problem.
Just I changed Explorer configuration for intranet and I could connect
like this way 'http://localhost:3000'
However,
I didn't find the way how to connect use URL like http://172.30.5.164:3000
I don't use socket.io module, just use basic express-generator template like GET/POST way.
I need how to connect on IE strongly because my project is related to OLE Automation, So I have to use ActiveXObject.
Anyone who give me the hint?
I'm not good at english writing, so i got to worry about that you understand my problem.
Thanks in advance.

There is a strange way IE handles local ip
see article.

Cannot host WebSocket Server - error during handshake

I want to try a WebSockets and I found this artcile on the internet Using WebSocket in .NET
I am sure that I did every step properly, I enabled WebSockets in IIS, I wrote all clases which are mention in article, I register HTTP Handler in web.config etc.. but when I want to try it I still get exception:
WebSocket connection to 'ws://localhost/CodeProjectWeb/WSHandler.ashx' failed: Error during WebSocket handshake: Unexpected response code: 404
I know that 404 probably means that URL is wrong, but how can be wrong? Some additional info: I am running on windows 10, IIS 10.0 Express, .NET 4.6, Visual Studio 2013, I tried it on Google Chrome, Firefox (both last versions).
To be honest, this is not first tutorial which I tried. I already tried antoher 3-4 articles about WebSocket in .NET, also I tried use SignalR but still with the same results. I just dont know, I think that I am missing some important little thing..
If you need some more information just ask but I hope I write everything

I finally figure it out (probably). I have to turn off Windows Firewall to make it work. So if you have similar problem just be sure that your Firewall is turn off.

net::ERR CONTENT LENGTH MISMATCH in Chrome with Jboss WildFly 8.2

I have JBoss wildFly 8.2 Up & Running on a windows machine with my war file deployed.
but my web page not able to load JS file and it shows error message in the web console as follows:-
"Failed to load resource: net:: ERR_CONTENT_LENGTH_MISMATCH"
I dig into the issue and found that server not able to load actual file size.
my js file is about to 90kb but server load 18kb and failed to load js file.
how to resolve this issue.
is this a Jboss configuration issue or Chrome issue.
please help me out.

I don't think it is related to jboss. I had the same issue of "net:: ERR_CONTENT_LENGTH_MISMATCH" when I was receiving a huge response in an ajax callback. It was working absolutely fine on Firefox and IE but the console error was there on chrome. Because of this the response was not loading on the UI. After further research I got to know, that Chrome was throwing this error for a special character i.e. "Æ" which was part of my json response body content. However, IE and Firefox were not having any complaint about this.
I corrected the DB value and removed the above special character from the server end. Everything started working fine on chrome as well.
My suggestion to check the body response you are sending from server end. It could be server side fix.
Regards,
Manoj

Configuring maximum number of simultaneous open WebSockets (in IE)

I've got this JS application. All client side JS communicating with a third party stream server via web sockets. I have about 18 different web sockets open for one page. Firefox and Chrome handle this many open web sockets at once just fine. IE11 seems to have a limitation of 4 open web sockets at once. Once I open that 5th web socket, regardless of socket call to the third-party server, I get an error thrown by IE, which closes the socket and gives the general error "SecurityError" and expanding the proto section it gives me . Seems to be pretty generic errors from my searches. At first I thought there may be a trusted zone type issue with IE, but I've added the client site to my trusted zone as well as the server providing the data.
This post provides info on max number of websockets for Firefox & Chrome, but I don't see anything specific about IE. Are there any known limitations to IE and web sockets? Answered, see edit below.
This MDN site talks about increasing the max value, but again, I can't find anything about IE. Is there some IE setting to up the amount of open connections? Answered: see below edit.
EDIT: This site shows the max connections settings for IE. It looks like it's a registry setting in Windows that controls the amount of web socket connections. Interestingly enough, I don't have that registry Key anywhere, but there is still a limit for this. The page speaks of IE10, and I'm working with IE11 specifically. Does anyone know if there are registry settings for this in regards to IE11? Has anyone just added these feature web socket registry keys and solved this issue?

The MSDN documentation you referenced is clear on the default being 6 concurrent connections (which means if not specified in the registry, that's what you'll get); and, if the documentation doesn't specify differently, it's probably safe to assume newer versions of Internet Explorer act in the same way as version 10.

Try setting through group policy. It worked for me.
https://jwebsocket.org/documentation/reference-guide/internet-explorer-tips

How may a web page that is loaded via https connect to a WebSocket server running on localhost?

I'm trying to create a web page that can connect to a client-local WebSocket server. The idea is to use the JavaScript client running in the browser as kind of a proxy to enable communication between the remote web server and the locally installed client application which implements the WebSocket service.
So basially, what I'd do is load a web page from https://example.com which includes some JavaScript that opens a new WebSocket to ws://localhost:1234/context.
This works fine as long as the web page is accessed via http. As soon as https is used, however, Firefox and Internet Explorer refuse to connect and the WebSocket constructor throws an exception (SecurityError, code 18).
Now, I already found advice from Mozilla stating that https sites should only use secure (wss://) WebSockets and plain http sites should only use plain WebSockets (link). But I don't really see the security issue when connecting to localhost from within an https context. Besides, this works like a charm for Chrome, Opera and Safari.
So the actual question is: Is there any way to work around this issue? Like introducing a non-https context inside the web page or something similar to get all browsers to connect to ws://localhost from within a https-delivered web page?
Thanks a lot in advance! I'm not exactly a web developer so this kind of browser-specific behaviour isn't really in my fields of expertise :)

You have to accept the cert first.
You can do this by simply going to https://localhost:1234/context, in your case. Once that's done, you can use the wss URL in your question.