|
|
You're in the
iis security
group:IIS 5.0 not accepting multipart/form-data
iis security:
I have 3 IIS server set up (Development, Test, and Production), and each of
them behave differently when submitting a multipart/form-data form. The Development server (using http://localhost/) works just fine, the file is uploaded, and the rest of the fields are set just fine. The Test server (using internal IP address) will send all the normal fields just fine, but does not upload the file. No error is generated for the browser, and the logs show a successful transaction (http: 302) The Production server (using public IP address that is routed through a firewall) does not upload the file, and does not send the rest of the fields, and the browser displays an error (which varies depending on the language used). When looking the web-logs, there is no error, in fact it shows that the everthing went fine (http: 302) Is this behavior caused by an IIS setting (or lack of setting) or a Windows setting? Where could I find these setting at? --
Are all the IIS servers the same version, same patches, etc?
I suggest using Network Monitor to see traffic between separate client and server doing the submit. This will tell you whether the data is sent by the browser or not, whether it is received/processed by the server or not, etc. Also use the same client machine as well as submit the exact same file to remove client-side variance. -- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in message news:598E4428-594A-434C-BB27-864AB50C3BD5@microsoft.com... I have 3 IIS server set up (Development, Test, and Production), and each of them behave differently when submitting a multipart/form-data form. The Development server (using http://localhost/) works just fine, the file is uploaded, and the rest of the fields are set just fine. The Test server (using internal IP address) will send all the normal fields just fine, but does not upload the file. No error is generated for the browser, and the logs show a successful transaction (http: 302) The Production server (using public IP address that is routed through a firewall) does not upload the file, and does not send the rest of the fields, and the browser displays an error (which varies depending on the language used). When looking the web-logs, there is no error, in fact it shows that the everthing went fine (http: 302) Is this behavior caused by an IIS setting (or lack of setting) or a Windows setting? Where could I find these setting at? -- CrazzyCodeMonkey
All the version of IIS are the same, all are fully patched, and all have the
most recent virus definitions loaded. The forms that reside on the three different servers (which is the exact same code) are all submitted from the same machine by the same browser. The Dev server is actually my Dell workstation, running Win2k Pro (hence the use of http://localhost) The Test server is a Dell server running Win2k Server. The Production server is a Dell server running Win2k Server. The browser I am using is Explorer 6.0.2800.1106. As for using Network Monitor, or some other packet sniffer, I honestly don't know what to look for. Some advice on what to look for would be appreciated. When the forms are submitted to the production server from outside the firewall, the same errors are received. The other 2 servers are protected by the firewall, and so can't test them from outsite the firewall. CrazzyCodeMonkey [quoted text, click to view] "David Wang [Msft]" wrote:
> Are all the IIS servers the same version, same patches, etc? > > I suggest using Network Monitor to see traffic between separate client and > server doing the submit. This will tell you whether the data is sent by the > browser or not, whether it is received/processed by the server or not, etc. > > Also use the same client machine as well as submit the exact same file to > remove client-side variance. > > -- > //David > IIS > This posting is provided "AS IS" with no warranties, and confers no rights.
Is URLScan running on all the machines? With the same configuration file?
Any other software differences? How large are the forms data being submitted? kilobytes, megabytes, gigabytes ? -- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in message news:76EB3352-37B8-4C79-85D0-018B6A9CC111@microsoft.com... All the version of IIS are the same, all are fully patched, and all have the most recent virus definitions loaded. The forms that reside on the three different servers (which is the exact same code) are all submitted from the same machine by the same browser. The Dev server is actually my Dell workstation, running Win2k Pro (hence the use of http://localhost) The Test server is a Dell server running Win2k Server. The Production server is a Dell server running Win2k Server. The browser I am using is Explorer 6.0.2800.1106. As for using Network Monitor, or some other packet sniffer, I honestly don't know what to look for. Some advice on what to look for would be appreciated. When the forms are submitted to the production server from outside the firewall, the same errors are received. The other 2 servers are protected by the firewall, and so can't test them from outsite the firewall. CrazzyCodeMonkey [quoted text, click to view] "David Wang [Msft]" wrote: > Are all the IIS servers the same version, same patches, etc? > > I suggest using Network Monitor to see traffic between separate client and > server doing the submit. This will tell you whether the data is sent by the > browser or not, whether it is received/processed by the server or not, etc. > > Also use the same client machine as well as submit the exact same file to > remove client-side variance. > > -- > //David > IIS > This posting is provided "AS IS" with no warranties, and confers no rights. > //
I actually found the solution to the solution on a Macromedia board
Using AC-MetaDataEditTool, I found that the UploadReadAheadSize was set to 0. Useing the MetaDataEditTool, simply delete this variable (LM/W3SVC/UploadReadAheadSize) and it works fine. CrazzyWebMonkey [quoted text, click to view] "David Wang [Msft]" wrote:
> Is URLScan running on all the machines? With the same configuration file? > Any other software differences? > > How large are the forms data being submitted? kilobytes, megabytes, > gigabytes ? > > -- > //David > IIS > This posting is provided "AS IS" with no warranties, and confers no rights. > // > "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in > message news:76EB3352-37B8-4C79-85D0-018B6A9CC111@microsoft.com... > All the version of IIS are the same, all are fully patched, and all have the > most recent virus definitions loaded. The forms that reside on the three > different servers (which is the exact same code) are all submitted from the > same machine by the same browser. > > The Dev server is actually my Dell workstation, running Win2k Pro (hence the > use of http://localhost) > The Test server is a Dell server running Win2k Server. > The Production server is a Dell server running Win2k Server. > > The browser I am using is Explorer 6.0.2800.1106. > > As for using Network Monitor, or some other packet sniffer, I honestly don't > know what to look for. Some advice on what to look for would be > appreciated. > > When the forms are submitted to the production server from outside the > firewall, the same errors are received. The other 2 servers are protected > by > the firewall, and so can't test them from outsite the firewall. > > CrazzyCodeMonkey > > "David Wang [Msft]" wrote: > > > Are all the IIS servers the same version, same patches, etc? > > > > I suggest using Network Monitor to see traffic between separate client and > > server doing the submit. This will tell you whether the data is sent by > the > > browser or not, whether it is received/processed by the server or not, > etc. > > > > Also use the same client machine as well as submit the exact same file to > > remove client-side variance. > > > > -- > > //David > > IIS > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > // > >
Hmm, UploadReadAheadSize is set to 49152 by default on all IIS versions, so
you ran some setup on the server that changed it. It also means that your POST acceptor likely has a bug. What happens when you POST data length > UploadReadAheadSize ? Try setting it to 1K and posting 2K of data. My hunch is that the POST acceptor won't read 2K of data. If so, this is a just a bug with the POST acceptor. -- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in message news:3AE5B050-ACC3-431F-8D74-85B6D9E92773@microsoft.com... I actually found the solution to the solution on a Macromedia board Using AC-MetaDataEditTool, I found that the UploadReadAheadSize was set to 0. Useing the MetaDataEditTool, simply delete this variable (LM/W3SVC/UploadReadAheadSize) and it works fine. CrazzyWebMonkey [quoted text, click to view] "David Wang [Msft]" wrote: > Is URLScan running on all the machines? With the same configuration file? > Any other software differences? > > How large are the forms data being submitted? kilobytes, megabytes, > gigabytes ? > > -- > //David > IIS > This posting is provided "AS IS" with no warranties, and confers no rights. > // > "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in > message news:76EB3352-37B8-4C79-85D0-018B6A9CC111@microsoft.com... > All the version of IIS are the same, all are fully patched, and all have the > most recent virus definitions loaded. The forms that reside on the three > different servers (which is the exact same code) are all submitted from the > same machine by the same browser. > > The Dev server is actually my Dell workstation, running Win2k Pro (hence the > use of http://localhost) > The Test server is a Dell server running Win2k Server. > The Production server is a Dell server running Win2k Server. > > The browser I am using is Explorer 6.0.2800.1106. > > As for using Network Monitor, or some other packet sniffer, I honestly don't > know what to look for. Some advice on what to look for would be > appreciated. > > When the forms are submitted to the production server from outside the > firewall, the same errors are received. The other 2 servers are protected > by > the firewall, and so can't test them from outsite the firewall. > > CrazzyCodeMonkey > > "David Wang [Msft]" wrote: > > > Are all the IIS servers the same version, same patches, etc? > > > > I suggest using Network Monitor to see traffic between separate client and > > server doing the submit. This will tell you whether the data is sent by > the > > browser or not, whether it is received/processed by the server or not, > etc. > > > > Also use the same client machine as well as submit the exact same file to > > remove client-side variance. > > > > -- > > //David > > IIS > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > // > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |