proxy.maud.bt.com

[booscreenofdef]

The proxy.maud.bt.com is removing support for self-signed certificates

More: Proxy server - Wikipedia

Please fix immediately

[Christopher_G]

Hi @booscreenofdef 

Welcome to the community.

This is above my level of understanding with this kind of thing, but I'll see if I can get someone to look into it. 

Could you give me a little more information about what this is impacting for you? It should help narrow down who I can raise it with.

Thanks

Chris

[WSH]

I think no one has responded because there is insufficient detail to understand what the OP is asking.  It also reads like a business query.  If so, it would perhaps be better posted on the business forum?

A self-sighed cert is only valid within your own network anyway, so surely you would expect a third-party like BT to reject it?  Presumably, I’m missing something here?

[Crimliar]

I cannot understand how the proxy associated with "Multicast-Assisted Unicast Delivery" would be using self assigned certificates, and it certainly shouldn't be relying on the same from an end-users device!

It's not a business query, it's a streaming query, and a very strange one at that!

[WSH]

Ah, MAUD’s a new one on me but from a quick read, it sounds like an overdue solution.  If it’s running as a proxy to cache streaming content then, presumably, the self-signed certificate is from a client accessing it from within its own network, so it makes a bit more sense now.

Said I was missing something.

Edit: From what I’ve just read, MAUD is a brand new thing developed by BT and still under test, so presumably BT supplied the proxy and this is an error it’s thrown?