<code>Sub TestPUT()IIS5, HTTP PUT, w2k
Set objInet = FormS!huvudform!InetCtrl.Object
objInet.Execute "http://111.222.333.444/put_test/attachments/test.txt", "PUT", "testing"
Debug.Print objInet.GetChunk(1024, icString)
End Sub</code>
<b>That works on a w2k3-server (IIS6)</b>
On a w2k I get this result:
<code><html><head><title>Method Not Supported</title></head>
<body><h1>The specified method is not supported</h1></body></html></code>
I´ve deinstalled urlScan.
If I try to put the data to a .asp-file,
<code>objInet.Execute "http://111.222.333.444/put_test/attachments/test.txt", "PUT", "testing"</code>
I get this response:
<code><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html dir=ltr>
<head>
<style>
a:link {font:8pt/11pt verdana; color:FF0000}
a:visited {font:8pt/11pt verdana; color:#4e4e4e}
</style>
<META NAME="ROBOTS" CONTENT="NOINDEX">
<title>The page cannot be found</title>
<META HTTP-EQUIV="Content-Type" Content="text-html; charset=Windows-1252">
</head>
<script>
function Homepage(){
<!--
// in real bits, urls get returned to our script like this:
// res://shdocvw.dll/http_404.htm#http://www.DocURL.com/bar.htm
//For testing use DocURL = "res://shdocvw.dll/http_404.htm#https://www.microsoft.com/bar.htm"
DocURL = document.URL;
//this is where the http or https will be, as found by searching for :// but skipping the res://
protocolIndex=DocURL.indexOf("://",4);
//this finds the ending slash for the domain server
serverIndex=DocURL.indexOf("/",protocolIndex + 3);
//for the href, we need a valid URL to the domain. We search for the # symbol to find the begining
</code>
(That is the same response that I got before deinstalling urlScan and sending a .txt-file)
I´ve spent some hours searching the web about this.
The best tip I´ve got is this
http://www.mcse.ms/archive155-2004-5-633348.html
But this is not my dilemma.
The key mentioned in the aricle does not exist on my server.
We also tried this on another w2k-server.
On that server it works, but we can´t see what differs the servers.
So I know that it can work on a w2k-server.
I´ve also matched the rights on disk (NTFS) on my w2k3 and w2k-server, and all looks ok.
Here is some of what I´ve found.
http://www.vbip.com/books/1861002750/chapter_2750_07.asp
http://www.derkeiler.com/Newsgroups/microsoft.public.inetserver.iis.security/2002-06/
http://www.webservertalk.com/archive120-2004-2-134367.html
http://www.officehelp.in/showthread.php?t=299634
http://www.mcse.ms/archive155-2004-5-633348.html
http://www.iis-resources.com/modules/newbb/viewtopic.php?topic_id=4206&forum=9
Any tip on this is welcome, if not solved, my only solution seams to be to upgrade/switch server to w2k3.