epolakis
epolakis
then cetcd will send the full payload towards etcd (100-continue will not be returned from etcd)
could it be that pidfile of the brick has a pid which was points to some other running process? If this is still reproducible, can you check the pid ?
thanks for the fast reply, yes thats true but payload (e.g. HTTP2 body in Captured packet payload chunck) can grow and exceed the 65K which would cause the whole HEP...
valid point about the overhead and NW packets but the issue is that with HTTP2 comes the encryption so duplication/mirroring on this level is tricky. would you consider to increace...
The intention is to use HEP to encapsulate HTTP2 for traffic monitoring. And in this case as can be seen in 3GPP 29.510 NFDiscovery responce includes an Array of NFProfile...
thank you i ll be waiting for the proposal- especially the backwards compatibility aspect
By the way, are there any other changes that you have in mind as part of the HEP4 or just the field size that we were discussing above ? Also,...
> it probably take a week - we are now busy with cloud launch. Thank you! thanks ! > I personally doubt this change alone would be worth releasing HEP4.......
Hi ! are there any news on this topic ? thx