<div dir="ltr"><div dir="ltr">Hi Daniel,<div><br></div><div>Thanks for your feedback.</div><div>I have a dedicated listen directive for JSONRPC</div><div><font face="monospace">listen = <a href="http://127.0.0.1:8000" target="_blank">127.0.0.1:8000</a></font><br></div><div><br></div><div>and then an event_route for it:</div><div><font face="monospace">event_route[xhttp:request] {<br> if ($Rp != 8000) {<br> xhttp_reply("403", "Forbidden", "text/html", "<html><body>Forbidden</body></html>");<br> exit;<br> }<br> if ($hu =~ "^/RPC") {<br> jsonrpc_dispatch();<br> } else {<br> xhttp_reply("200", "OK", "text/html", "<html><body>Wrong URL $hu</body></html>");<br> }<br> return;<br>}<br></font></div><div><br></div><div>So, I'm already doing HTTP traffic only in port 8000.</div><div>The interesting part is that if I use kamcmd pl.list pipe_INVITE, only the first log line is printed. Using curl, I see the other 2 logs all the time.</div><div><br></div><div>Thank you</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 21, 2020 at 2:45 PM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hello,</p>
<p>can you want the traffic on port 8000 and see if there is no
"unexpected" traffic there? There should be no error message for
parsing the first line of an HTTP request.</p>
<p>The error message related the missing pipe can be made debug.<br>
</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div>On 21.01.20 15:34, Nuno Ferreira wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>I'm using pipelimit with the "clean_unused" option to get
rid of pipes that are not used for quite some time. At the
same time we are monitoring pipelimit with a jsonrpc call
similar to:</div>
<div><br>
</div>
<div><font face="monospace"># curl --header 'Content-Type:
application/json' --data-binary '{"id": 1, "jsonrpc": "2.0",
"method": "pl.list", "params": ["pipe_INVITE"]' <a href="http://127.0.0.1:8000/RPC" target="_blank">http://127.0.0.1:8000/RPC</a><br>
<br>
</font></div>
<div><font face="arial, sans-serif">Reply:</font></div>
<div><font face="monospace">{<br>
"jsonrpc": "2.0",<br>
"error": {<br>
"code": 400,<br>
"message": "Unknown pipe id pipe_INVITE"<br>
},<br>
"id": 1</font><br>
</div>
<div><font face="monospace">}</font></div>
<div><br>
</div>
<div>The above reply is valid because the pipe_INVITE was not
loaded yet, but the request makes kamailio to log the
following log messages:</div>
<div><br>
</div>
<div><font face="monospace">Jan 20 11:21:48 proxy1
kamailio[24474]: ERROR: pipelimit [pl_ht.c:519]:
rpc_pl_list(): no pipe: pipe_INVITE<br>
Jan 20 11:21:48 proxy1 kamailio[24474]: ERROR: <core>
[core/parser/parse_fline.c:262]: parse_first_line():
parse_first_line: bad message (offset: 20)<br>
Jan 20 11:21:48 proxy1 kamailio[24474]: [466B blob data]</font></div>
<div><br>
</div>
<div>Since the monitoring system does periodic requests, those
log lines get a bit annoying and fill the log with ERROR
messages that aren't really errors.</div>
<div><br>
</div>
<div>IMHO the first log line should be converted to DEBUG
instead of ERROR, but I have some doubts about the one
from parse_fline.c:262. parse_first_line() is used to process
both SIP and HTTP. It makes sense to log ERROR if SIP but not
in the case of HTTP...</div>
<div>Regarding the "[466B blob data]" I really don't know from
where it's coming from.</div>
<div>I can submit a PR, but I would like to have first some
feedback from you.</div>
<div><br>
</div>
Thank you,
<div><br>
</div>
<div>Nuno<br clear="all">
<div><br>
</div>
</div>
</div>
<br>
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">*Confidentiality
Notice: The information contained in this e-mail and any</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">attachments
may be confidential. If you are not an intended recipient, you</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">are
hereby notified that any dissemination, distribution or copying
of this</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">e-mail
is strictly prohibited. If you have received this e-mail in
error,</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">please
notify the sender and permanently delete the e-mail and any</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">attachments
immediately. You should not retain, copy or use this e-mail or</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">any
attachment for any purpose, nor disclose all or any part of the</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">contents
to any other person. Thank you.*</span>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Kamailio (SER) - Users Mailing List
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<pre cols="72">--
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">www.asipto.com</a>
<a href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - March 9-11, 2020, Berlin - <a href="http://www.asipto.com" target="_blank">www.asipto.com</a>
Kamailio World Conference - April 27-29, 2020, in Berlin -- <a href="http://www.kamailioworld.com" target="_blank">www.kamailioworld.com</a></pre>
</div>
</blockquote></div><div><br></div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><p style="font-family:Arial;color:rgb(0,0,0);font-size:12px"></p></div></div></div></div></div></div></div></div></div></div></div>
</div>
<br>
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">*Confidentiality Notice: The information contained in this e-mail and any</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">attachments may be confidential. If you are not an intended recipient, you</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">are hereby notified that any dissemination, distribution or copying of this</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">e-mail is strictly prohibited. If you have received this e-mail in error,</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">please notify the sender and permanently delete the e-mail and any</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">attachments immediately. You should not retain, copy or use this e-mail or</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">any attachment for any purpose, nor disclose all or any part of the</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">contents to any other person. Thank you.*</span>