Well the good news is that I managaed to get this working!! It seems the 403 message may have been misleading?
I started playing with the file – reducing it's size and then upping it until I hit problems. When it reached 48K I got "Chunked encoding upload is not supported on the HTTP/1.0 protocol."
Official Microsoft reason for the problems: You cannot disable HTTP chunked encoding in BizTalk Server 2004.
Explanation: Microsoft BizTalk Server uses chunked encoding in HTTP transport when the message size is more than 48 KB. Sometimes, you may not want to use chunked encoding. For example, you may have to disable the chunked encoding when the other end of the HTTP transport cannot receive chunked encoding.
Solution: Either stop production of files larger than 48K, or install Service Pack 2 and then make some amendments to the machine registry to enable larger files through —
After you install the fix, you must add the DisableChunkEncoding registry value to disable chunked encoding for outbound requests and responses to inbound requests. The registry value is a DWORD type. To disable chunked encoding, set the registry value to 1. By default, the registry value is 0.
For outbound requests, you must add this registry value under each registry key that matches this pattern:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc{Host instance GUID}For inbound requests, you must add this registry value under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc 3.0\HttpReceive
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
As i said – good news is that it now works fine for large files!!
blems: You cannot disable HTTP chunked encoding in BizTalk Server 2004.
Explanation: Microsoft BizTalk Server uses chunked encoding in HTTP transport when the message size is more than 48 KB. Sometimes, you may not want to use chunked encoding. For example, you may have to disable the chunked encoding when the other end of the HTTP transport cannot receive chunked encoding.
Solution: Either stop production of files larger than 48K, or install Service Pack 2 and then make some amendments to the machine registry to enable larger files through —
After you install the fix, you must add the DisableChunkEncoding registry value to disable chunked encoding for outbound requests and responses to inbound requests. The registry value is a DWORD type. To disable chunked encoding, set the registry value to 1. By default, the registry value is 0.
For outbound requests, you must add this registry value under each registry key that matches this pattern:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc{Host instance GUID}For inbound requests, you must add this registry value under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc 3.0\HttpReceive
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
As i said – good news is that it now works fine for large files!!