Server Name Bug in EWS behavior of new HP OfficeJet Pro 9015e

[basezen]

Hi, brand new printer HP OfficeJet Pro 9010 just installed, firmware latest at MANHTNPP1N005.2242A.00, running in US.

Hang on to your hats, this gets pretty technical, so would have to get escalated fairly high to get an answer.

There's an obscure bug in the embedded web server that prevents us from accessing the printer EWS using an internally maintained FQDN. This seems to be a fairly infrequent use case and thus probably has not received much attention.

We use internal FQDNs (fully qualified domain names), so our printer's name is xyz-printer.company.com. DHCP is set up to set the host name to xyz-printer, and send the domain setting of "company.com". Additionally, the host name and domain name within the EWS IPv4 settings is identical.

We can access the EWS at: https://xyz-printer.company.com/ and the skeleton of the page loads fine, but it is otherwise totally broken on account of the fact that the critical helper resource: /DevMgmt/SecurityCap.xml returns HTTP 403 (Forbidden). The AJAX code running on the site does not check for this error and crashes on a JSON parse error.

The embedded nginx web server is only serving that particular XML resource when the Host header is set to the IP address, OR https://xyz-printer/, OR https://xyz-printer.local (the configured Bonjour name). But it will NOT serve it when the Host header is set to our internal FQDN xyz-printer.company.com.

This becomes an annoyance for our internal certificate system, because we've installed (successfully) a custom certificate for xyz-printer.company.com.

To be clear, this is totally independent of the client side -- I've verified the behavior with MacOS, Windows, and even command-line curl.

I've not seen this bug with *other* HP printers, so I'm befuddled. Crossing my fingers that this can escalate to the right software development team!!

Cheers,

Daniel