QuincyGao created an issue (kamailio/kamailio#4176)
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature
requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration
file, ask on sr-users mailing list:
*
https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio.org/
If you have questions about developing extensions to Kamailio or its existing C
code, ask on sr-dev mailing list:
*
https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.org/
Please try to fill this template as much as possible for any issue. It helps
the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that
includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment
that
includes the token `/notstale`. Also, any comment postpone the `expire`
timeline,
being considered that there is interest in pursuing the issue.
If there is no content to be filled in a section, the entire section can be
removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a
comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
I confirmed the problem again， HTTP GET, POST without body is ok, HTTP post
with json body can't return message and block. microhttpd1.0.1 installed.
```
curl -d '{"test":"2", "test2":"1"}' -H "Content-Type: application/json" -X
POST http://172.16.4.111:8284
```
kamailio.cfg
```
loadmodule "microhttpd.so"
modparam("microhttpd", "listen_addr", "172.16.4.111")
modparam("microhttpd", "listen_port", 8284)
event_route[microhttpd:request] {
xinfo("request: $mhttpd(method) - url: $mhttpd(url) - data:
[$mhttpd(data)]\n");
mhttpd_reply("200", "OK", "text/html","<html><body>OK</body></html>");
#mhttpd_reply("200", "OK", "application/json","\{\"code\":0\}");
}
```
```
ldd /usr/local/lib64/kamailio/modules/microhttpd.so
linux-vdso.so.1 => (0x00007ffda77fc000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f5c6d357000)
libm.so.6 => /lib64/libm.so.6 (0x00007f5c6d055000)
librt.so.1 => /lib64/librt.so.1 (0x00007f5c6ce4d000)
libmicrohttpd.so.12 => /usr/local/lib64/libmicrohttpd.so.12
(0x00007f5c6cc1a000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5c6c9fe000)
libc.so.6 => /lib64/libc.so.6 (0x00007f5c6c630000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5c6d765000)
ll /usr/local/lib64/libmicrohttpd.*
-rw-r--r--. 1 root root 1902020 Mar 6 11:19 /usr/local/lib64/libmicrohttpd.a
-rwxr-xr-x. 1 root root 998 Mar 6 11:19 /usr/local/lib64/libmicrohttpd.la
lrwxrwxrwx. 1 root root 24 Mar 6 11:19 /usr/local/lib64/libmicrohttpd.so
-> libmicrohttpd.so.12.62.1
lrwxrwxrwx. 1 root root 24 Mar 6 11:19
/usr/local/lib64/libmicrohttpd.so.12 -> libmicrohttpd.so.12.62.1
-rwxr-xr-x. 1 root root 992136 Mar 6 11:19
/usr/local/lib64/libmicrohttpd.so.12.62.1
```
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full
backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by
Kamailio, add them next, or attach to issue, or provide a link to download them
(e.g., to a pastebin site).
-->
```
25(2379) DEBUG: microhttpd [microhttpd_mod.c:475]: ksr_microhttpd_request():
executing event_route[microhttpd:request] (3)
25(2379) exec: *** cfgtrace:dbg_cfg_trace(): request_route=[microhttpd:request]
c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=1181 a=25 n=xinfo
25(2379) INFO: <script>: request: POST - url: / - data: [{"test":"2",
"test2":"1"}]
25(2379) exec: *** cfgtrace:dbg_cfg_trace(): request_route=[microhttpd:request]
c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=1182 a=28 n=mhttpd_reply
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with
ngrep or save in a pcap file, then add them next, or attach to issue, or
provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally,
provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.8.5 (x86_64/linux)
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu
16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
Centos7.9
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4176
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4...@github.com>_______________________________________________
Kamailio - Development Mailing List -- sr-dev@lists.kamailio.org
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
