@MarkKaplun Hm... Could you expand on the "many points"? Which would those be?

@ThatBrazilianGuy I can't help but notice that your payload is not JSON yet your headers insist it is

perhaps you should fix that

I also see that you never check the response. The response may hold the answers you seek

I very much doubt that docker is the problem

@ThatBrazilianGuy sorry, that was just a figure of speech, but you could have configuration problems at OS level, docker level or the integration between them. It might even be that your packet inspector fails to properly analyze things comming from docker.

Maybe you should try to use "bare" curl first and if you still see the same, ask about it in some docker forum

@ThatBrazilianGuy for the record I do not believe in otto's answer. that SE question he points to is 10 years old, but that does give a clue for further investigation.

first check that there is no reply to the first 1024 packet.

Hiya! Would someone mind explaining this to me before I go nuts. Adding a class name using the nav_menu_css_class filter which contains a double underscore causes the pages rendering navs to error out. One works. Three works. No bueno with 2

@Sean hmm do you have a Q on the main site with code we can look at?

@TomJNowell Not yet, I'm trying to find the error logs on this box to see what's actually going on. It's a fresh install, bare bones theme with no plugins and nothing else hooking into it.

oooh it fatal errors?!

Aye

I'm like 99% convinced it's localised but it's just bizarre being a new install. :P

Yep. Nevermind. Found it. Turns out I'm just tired and dumb. PEBCAK. Sorry!

PEBCAK? What was the problem?

Building a footer nav and there's nothing after it on the page. The server had opcache running which cached a syntax earlier in the testing & rendered everything up to the menu. I switched off the cache but saw the same problem. Turns out it wasn't a fatal. The logs were showing nothing because it had started working. The CSS class with the double underscore had rules to hide the list/menu formatting as intended, so the syntax error and working result looked exactly the same on the page.

Turns out I thought it was bugged because it was working. Go figure