Bug 1805484 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
This is causing a failure in bundle.https.html

Spec says that when using 'max-bundle', and the other side does not do bundle, we should only use one m-section. Right now, that will happen when we are the offerer (through the use of a=bundle-only), but when we're the answerer we will open the extra transports. I'm guessing we have a similar bug for 'balanced'.

I doubt this actually breaks anything in practice, but we should fix.
Revision 1 by
on 
This is causing a failure in bundle.https.html

Spec says that when using 'max-bundle', and the other side does not do bundle, we should only use one transport, on the first m-section. Right now, that will happen when we are the offerer (through the use of a=bundle-only), but when we're the answerer we will open the extra transports. I'm guessing we have a similar bug for 'balanced'.

I doubt this actually breaks anything in practice, but we should fix.

Back to Bug 1805484 Comment 0