Re: [reSIProcate-users] Cryptic logs on SSL_read
I may have been responsible for this being in there - it was being
logged at the lowest severity, STACK, because it is not very useful or
important in most scenarios but there was some value in it when I was
trying to get this code merged in the first place.
Can you clarify what you mean when you say it makes the log unusable?
Does it actually cause additional corruption in your log reading tool?
You should have been able to see a decoded version of the data further
down in the log.
On 23/04/15 21:48, Scott Godin wrote:
> Thank Jorge! I have commented out the offending log lines.
>
> Best Regards,
> Scott
>
> On Thu, Apr 23, 2015 at 3:30 AM, Jorge Bustamante
> <jbustamante@xxxxxxxxxxxxx <mailto:jbustamante@xxxxxxxxxxxxx>> wrote:
>
> This seems to be caused by WebSocket masking... messages are being
> printed right after SSL_read before being unmasked by WebSocket
> code, thus the wild characters.
>
> This makes logs with RESIP-Stack level unusable... is there any plan
> to fix this?
>
> Regards,
> Jorge Bustamante
>
> On Wed, Apr 15, 2015 at 2:36 PM, Jorge Bustamante
> <jbustamante@xxxxxxxxxxxxx <mailto:jbustamante@xxxxxxxxxxxxx>> wrote:
>
> Hi,
>
> Resiprocate logs when using WSS show a lot of invalid characters
> which make logs hard to read. I am using resiprocate 1.9.7. Is
> this a known issue?
>
> RESIP-Stack: SSL_read returned 403 bytes
>
> [�^A��ρ^?Ζ�_���E���I���I���L��J��Q���E���O���^^��^P���^H���,ş�M���uڦ�E���/��O���,���^R���^T���^Q���^Q��^V���^M��^W���^W���4���F���u���Rʠ�^H��^L��F���^P��^L
> 忻
>
> M��K���F���^M��^L��^S��Q��A���^X���^Y���J�<8b>9���E���^V���O��N��Ḽ�^P��^P��^^^\
> 㢿D��B���^T��^^?uϮ�^S���E���^S���^L���J���^X���^O�<8b>
>
> <ߪ�E��K���&�<8b>,��^P���^[���^^�_��^]��^[���^M�uټ�^M���^Z_ν�^^��^Y���^Z��<���^V��_��Q��O�<8b>
> <��^Z⻬3��^K���O�Ōu]
>
> Regards,
> Jorge Bustamante
>
>
>
>
> This email is intended solely for the person or entity to which it
> is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient and have received
> this email in error, please notify BroadSoft, Inc. immediately by
> replying to this message, and destroy all copies of this message,
> along with any attachment, prior to reading, distributing or copying it.
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> <mailto:resiprocate-users@xxxxxxxxxxxxxxx>
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>
>
>
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>