daniele001 wrote I got the problem with the proxy. it's a strange story, in the label it's written "Domain\username:" if I enter DOMAIN\myusername I get the security error of the proxy for the authentication. If I enter just the username I've fully operational the URL  of the xml source......

Do you mean inside the XML source settings? This has nothing to do with the proxy settings, it is used for authentification against the server

daniele001 wrote Just for your info I'm forced to do the same in DNN host proxy settings.   Another problem is the use of the URL for the XSL, in this case I always get the following error :  System.Net.WebException The remote server returned an error: (401) Unauthorized  In this case I've just few XSL that I use in my portal, so I use the internal file system and this works, but... just to let you know this possible issue.

It seems that your XML and XSL sources are stored on servers that do not allow to access these files as anoymous. Only the request to query the XML source supports also user based authenification. Do you need that also for XSL scripts? Can you please explain the use case?

daniele001 wrote Last. in each XML/XSL module I need to specify user and password. Without this I get proxy security error. The only problem is that every time I need to save the module, like after a change, I MUST renter the pasword again..... Thank you very much for your patience... I appreciate your help. Have a great day Daniele

I added the password issue inside the tracker : http://support.dotnetnuke.com/Default.aspx?p=16&i=5880