<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/02/14 10:26, Peter Dunkley wrote:<br>
</div>
<blockquote
cite="mid:CAEqTk6TBVjiHo3o8zBZWMab4R_qvqCQJmNWDG695Vfc5Px-Jmw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">Hello,
<div><br>
</div>
<div>I don't think this is relevant to the Kamailio
implementation.</div>
<div><br>
</div>
<div>The Kamailio implementation doesn't do anything with
headers like Cookie: at all. If an implementer of a Kamailio
solution wants to do anything with the Cookie: header (or any
other), they can do whatever they want using the Kamailio
configuration file "programming language".</div>
<div><br>
</div>
<div>You can make use of all of the standard Kamailio
header/parameter selects and transformations to help you do
whatever you want with these headers.</div>
</div>
</blockquote>
<br>
Just to clarify: we are talking about HTTP Cookie headers sent
during the WebSocket handshake, not about a Cookie header in any SIP
message<br>
<br>
Does the Kamailio WebSocket transport provide access to the HTTP
WebSocket handshake headers and their contents or only the SIP
headers?<br>
<br>
Is there a way to invoke some route block in the configuration file
to examine the HTTP headers and decide whether a WebSocket
connection will be accepted?<br>
<br>
</body>
</html>