I don’t know if “proxy software name” can be changed.
And I highly doubt that this is the problem. When a web browser uses proxy (explicitly configured, not transparent proxy), then it actually requests proxy server to open a TCP connection towards https server and then it uses that connection in a “tunnel” manner … i.e. proxy doesn’t do anything about traffic passed, it doesn’t do anything about certificates, no nothing. And hence server doesn’t see MT Proxy as being a peer (client info is part of end-to-end encrypted traffic).
I was referring specifically to MT’s proxy implementation, this is the only relevant according to your question.
It’s not fair to compare full-blown software with “functionality-wise similar” parts in ROS … because ROS functions are most of time severely space-restriced and often performance-restricted.
The “proxy name” is only sent to the peer when the request is http.
Probably the proxy test you use is a http page.
However in today’s internet, there are almost no real pages that use http, everything uses https.
When the proxy operates in https mode, it does not (it cannot) insert information in the bytestream.
There also is no errorpage from the router in https mode. There cannot be one.