I think this response is borderline. RFC3261 specifically mandates SINGLE
character to be used, however the reason phrase might contain as many
spaces as needed, so that it can be argued that in this particular case the
reason phrase is " OK" versus "OK" normally.
---
7.2
>
> *From: *Users on behalf of Антон Ершов
>
> *Reply-To: *OpenSIPS users mailling list
> *Date: *Friday, February 14, 2020 at 12:01 PM
> *To: *OpenSIPS users mailling list
> *Subject: *Re: [OpenSIPS-Users] rewrite status-line
>
>
>
> I understand correctly that o
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] rewrite status-line
I understand correctly that on my side I can not fix this problem?
пт, 14 февр. 2020 г. в 17:17, Антон Ершов
mailto:suhari...@gmail.com>>:
They can not
пт, 14 февр. 2020 г., 17:10 johan mailto:jo...@demo
I understand correctly that on my side I can not fix this problem?
пт, 14 февр. 2020 г. в 17:17, Антон Ершов :
> They can not
>
> пт, 14 февр. 2020 г., 17:10 johan :
>
>> To me 200 OK is perfectly valid. The operator should fix this at his
>> side.
>> On 14.02.20 15:01, Антон Ершов wrote:
>>
They can not
пт, 14 февр. 2020 г., 17:10 johan :
> To me 200 OK is perfectly valid. The operator should fix this at his
> side.
> On 14.02.20 15:01, Антон Ершов wrote:
>
> Hello friends!
> we have final equipment that does not meet 200OK correctly. it adds an
> extra space between 200 and OK.
To me 200 OK is perfectly valid. The operator should fix this at his
side.
On 14.02.20 15:01, Антон Ершов wrote:
Hello friends!
we have final equipment that does not meet 200OK correctly. it adds an
extra space between 200 and OK. from the point of view of rfc is not
very scary. but there
