| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
Well, I guess if I make a plugin that rewrites request/response headers according to my call logic and maintains the state then repro may act as a b2bua. But I'm not sure whether it will possible to maintain the Client and Gateway transactions separate enough by rewriting request/response headers only. The idea is to to fix To, From headers and the Request-URI,
allowing other headers pass through. Will it be enough for proxy
to act as a b2bua? Regards, Roman Rybalko
From: Scott Godin
Sent: Tuesday, March 27, 2018 9:38PM +0300 To: Roman Rybalko Cc: Resiprocate-users Subject: Re: [reSIProcate-users] Authorization by Proxy to Gateway A proxy is not supposed to modify headers, it is
supposed to only add headers involved in routing (ie: Via, Route
and/or Record-Route headers). It might also remove some headers
to (ie: Identity headers) when forwarding outside of it's domain.
I suggest a good read through the proxy behaviour sections in
RFC3261. You might be able to add the Authentication headers, but
you will definitely run into trouble, if you start trying to
change the To and/or From headers. If you need to modify key
headers like To/From then you must write a B2BUA instead.
FYI the challenge realm/domain will be in the 407/401
response. You could use this to find the correct user.
Scott
|