[xmlsec] xmlSecIORegisterCallbacks problems

Fri, 06 Jun 2003 08:33:28 -0700

This is a multi-part message in MIME format.
--------------090808020209020905000507
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

xmlSecIORegisterCallbacks() is used by xmlsec to fetch binary
files when xmlRegisterInputCallbacks() is used by xmlsec/libxml
to fetch xml files. The reason for this is that default libxml
callbacks un-compress gzipped files and in xmlsec we *want* to
download binary files "as-is".

If you provide your own HTTP/FTP client then you should probably
register your functions in both xmlsec and libxml. Please note,
that by default xmlsec loads its own callbacks so you would probably
need to cleanup the callbacks list before adding yours.

To check that it works, set a breakpoint in your functions and
see would it be called or not. All xmlsec IO is done thru these
callbacks and it would surprise if something is broken there.

Aleksey

--------------090808020209020905000507
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
 <title></title>
</head>
<body>
xmlSecIORegisterCallbacks() is used
by xmlsec to fetch binary 
files when xmlRegisterInputCallbacks()
is used by xmlsec/libxml 
to fetch xml files. The reason for this is that default libxml 
callbacks un-compress gzipped files and in xmlsec we *want* to 
download binary files "as-is". 
 
If you provide your own HTTP/FTP client then you should probably 
register your functions in both xmlsec and libxml. Please note, 
that by default xmlsec loads its own callbacks so you would probably 
need to cleanup the callbacks list before adding yours. 
 
To check that it works, set a breakpoint in your functions and 
see would it be called or not. All xmlsec IO is done thru these 
callbacks and it would surprise if something is broken there. 
 
Aleksey 
 
 
 
 
 
 
 
</body>
</html>

--------------090808020209020905000507--