Commented Unassigned: CombineScriptsHandler getting registered with full URL instead of relative path [27549]

When the "CombineScriptsHandler" is registed in the "web.config", and enabled via setting the "CombineScripts" to true on the "ToolkitScriptManager", the handler appears to be getting registered with the full website URL (see attachment) instead of using a relative path like the ones used by "ScriptResource.axd" and "WebResource.axd".

This seems to be causing issues when making use of SSL over a non-standard port (ie. multiple site Windows Azure development server) as the port appears to be getting dropped from the absolute URL.

The handler should work similar to how "ScriptResource.axd" and "WebResource.axd" do in regards to registering itself on the page in order to prevent JavaScript errors due to the combined script not being found due to invalid path.



Comments: I've found two workarounds: 1. Set the (deprecated) property CombineScriptsHandlerUrl of ToolkitScriptManager to null. Best way to do this is a PageAdapter 2. Remove the CombineScriptsHandler.axd from your web.config Both solutions will force ACT to add a relative Url to your page with the script combine params. Script combine will still work ``` <script src="/MyVDir/MayBeAnySubDirectory/MyPage.aspx?_TSM_CombinedScripts_=True&amp;v=KEBLo4hJw4lJ4Yuq9AnTZDb7wFUt4x17WaZT8Df5dxI1&amp;_TSM_Bundles_=&amp;cdn=False" type="text/javascript"></script> ```