ipaddress | handle IP addresses | TCP library

The problem is that string literals "this is a string literal" are of type char[] in C but const char[] in C++. So if you have sloppily written C code which doesn't use const correctness of function parameters, that code will break when ported to C++. Because you can't pass a const char* to a function expecting char*.

And no, it is generally not safe to "cast away" const - doing so is undefined behavior in C and C++ both.

The solution is to fix the original C code. Not using const correctness is incorrect design, both in C and C++. If the C++ compiler supports compound literals, then one possible fix could also be:

WiFi channels 12-14 are not used in some countries (e.g. US). Perhaps the ESP32 AP picked one of those channels, and ESP8266 is configured by default with settings from a country which doesn't allow them. Set the AP channel to some reasonably safe value in range 1-11.

I can see that the default channel should be 1, but I'd suggest experimenting with it, perhaps setting it to 6:

As mentioned in comments your xml document has namespace definitions in its DocumentElement (xmlns stands for xml name space). Furthermore "it contains a default namespace so any attempted parsing on named nodes must map to this namespace URI otherwise returns nothing."

To allow eventual analysis it's necessary to include a user defined prefix (e.g. :s) into explicit namespace settings, which can be used in later XPath expressions:

With your shown samples please try following. Please make sure to clear browser cache before testing your URLs.

You can try this:

1. Add the X-Forwarded-For to the "HTTP Request Headers" (goto the API-Gateway configuration -> Resources -> Method Request).
2. Add a Template with Content-Type: application/json (Resources -> Integration Request -> "Mapping Templates")
3. Add a Mapping to the template

This problem turned out to be a red herring, with the real issue found by looking at IIS application logs within the docker container. I suggest anyone facing this to open up powershell in the container by running:

docker container exec -it powershell

Then browse the application logs with:

Get-EventLog -LogName Application -Newest 15

You may see an issue there. Also, you can try running this in the container to see if an error is spit out:

Invoke-WebRequest http://localhost

Your mistake is that you pushed MenuPage to stack in OtpScreen

Parsing a recursive grammar always takes some extra thinking. One step I always always always encourage parser devs to take is to write a BNF for your syntax before writing any code. Sometimes you can do this based on your own original syntax design, other times you are trying to reconstruct BNF from example text. Either way, writing a BNF puts your brain in a creative zone instead of coding's logical zone, and you think in parsing concepts instead of code.

In your case, you are in the second group, where you are reconstructing a BNF based on sample text. You look at the example and see that there are parts that have names, and that it looks like a nested dict would be a nice target to shoot for. What are the things that have names? Some things are named by a 'name = a-value' kind of arrangement, other things are named by 'name structure-in-braces'. You created code that follows something like this BNF:

127.0.0.1 is localhost which means by definition the server is only reachable on the same host.

If you want the server to listen on all interfaces don't specify IPAddress.Any respectively IPAddress.IPv6Any or use 0.0.0.0.