Closed #3723.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3723#event-12193921070
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mailing
This PR is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3723#issuecomment-1982229451
You are receiving this because you are
Even adding the http url value as parameter to r-uri is not safe, because its
value can have special characters that have different meaning.
If you need to do something async in xhttp, then you have to add something
specific for http requests, knowing the complexity of processing for SIP
transa
You are right, there are many ways to solve the problem. The presence of an
HTTP server in kamailio allows you to implement microservices and I suggested
expanding its use. I don’t think I can convince you otherwise, but kamailio has
long become a multifunctional tool necessary for processing SI
First, this is not a fix, the http traffic was never supposed to be fully
handled as sip traffic. Kamailio is not a full HTTP server/proxy. The
workaround for creating a fake sip message was done for local processing,
mainly to be able to use authentication and authorization functions as well as
