OK, I digged around a bit, and after your second edit I found this bug on the issue list. I doesn’t state whether this was encountered under cygwin or not, but the error that it is hitting leads down to this piece of code: uint16_t * twobytebuf = new uint16_t[buflen]; str->Write(twobytebuf, 0, buflen, String::HINT_MANY_WRITES_EXPECTED); for … Read more
Those look much like Bonjour / mDNS requests to me. Those packets use multicast IP address 224.0.0.251 and port 5353. The most likely source for this is Apple iTunes, which comes pre-installed on Mac computers (and is a popular install on Windows machines as well). Apple iTunes uses it to discover other iTunes-compatible devices in … Read more
API Gateway and Load Balancer are 2 different things. Load Balancer -> Its a software which works at protocol or socket level (eg. tcp, http, or port 3306 etc.) Its job is to balance the incoming traffic by distributing it to the destinations with various logics (eg. Round robin). I doesn’t offer features such as … Read more
Sorry, all you get is what you see in document.cookie. The cookie metadata like path, domain and expires are not visible to site code (neither to JavaScript nor to the server-side). To read a cookie that is being shadowed by a cookie with a more-specific domain or path, the only thing you can do is … Read more
I’ve been researching the topic a bit lately and so far my (theoretical) conclusions are as follows: Browser support is high for both as of November 2022, when counting the real global usage of browsers (~94% vs ~83%) dns-prefetch = DNS and preconnect = DNS + TCP + TLS. Note that DNS lookup is quite … Read more
You do not assign a domain to a node.js server, instead you load your app onto a machine which has an ip adress, which in your case is 42.12.251.830:4000. You then need to make sure your app is listening on the correct port, which on most servers is 80 using express it’s as simple as … Read more
The fully qualified domain name is returned by socket.getfqdn().