Hello 'serusers,
I would love a quick hint ...
what is the difference between www_authorize and proxy_authorize ?
I heard that the second is to prefer, but in many examples that I used for my config I have seen the first ...
Tnx !
On 12-02 17:01, Alessio Focardi wrote:
Hello 'serusers,
I would love a quick hint ...
what is the difference between www_authorize and proxy_authorize ?
www_authorize is usually used when the entity generating it is the final destination of the request. Registrar uses www_authorize, for example. When ser reiceives a REGISTER, it will not forward it anywhere but it will process it internally using save("location"). In this situation www_authorize should be used.
When ser receives an INVITE, it will (optionally) look up the Request URI in the location database and then forward it. In this case proxy_authorize should be used because ser will forward the request.
The only difference between the two commands is the name of header fields used for digest challenge and response.
Jan.
Jan Janak wrote:
On 12-02 17:01, Alessio Focardi wrote:
what is the difference between www_authorize and proxy_authorize ?
www_authorize is usually used when the entity generating it is the final destination of the request. Registrar uses www_authorize, for example. When ser reiceives a REGISTER, it will not forward it anywhere but it will process it internally using save("location"). In this situation www_authorize should be used.
When ser receives an INVITE, it will (optionally) look up the Request URI in the location database and then forward it. In this case proxy_authorize should be used because ser will forward the request.
The only difference between the two commands is the name of header fields used for digest challenge and response.
So for a SUBSCRIBE, I guess that www_authorize is used?
/O
On 12-02 19:29, Olle E. Johansson wrote:
Jan Janak wrote:
On 12-02 17:01, Alessio Focardi wrote:
what is the difference between www_authorize and proxy_authorize ?
www_authorize is usually used when the entity generating it is the final destination of the request. Registrar uses www_authorize, for example. When ser reiceives a REGISTER, it will not forward it anywhere but it will process it internally using save("location"). In this situation www_authorize should be used.
When ser receives an INVITE, it will (optionally) look up the Request URI in the location database and then forward it. In this case proxy_authorize should be used because ser will forward the request.
The only difference between the two commands is the name of header fields used for digest challenge and response.
So for a SUBSCRIBE, I guess that www_authorize is used?
It depends. A proxy (ser without pa module) forwarding SUBSCRIBER will use proxy_auhorize, presence server (ser with pa module) will use www_authorize.
Jan.
-
Alessio Focardi -
Jan Janak -
Olle E. Johansson