[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: http_url_post_stmf



Hello,

On 1/27/2012 11:05 AM, David Huls wrote:
> Trying to test new function and we do not get a 302 back.  The response
> file returned contains this error: Unknown error: There is not enough
> space on the disk.

302 means that it's redirecting you.  (asking you to visit another URL). 
  The response you're getting now (200) means "success". I don't see why 
that'd be suspicious to you... that seems like the normal, desired 
response.  Unless they told you to expect a 302?


> Attached is the debug log. Can anyone see an issue.

I see two strange things in the request you are submitting to them:

1) You have a ton of extra blanks at the end of your URL. I don't know 
if this matters to the server or not, but it could potentially.

2) You aren't sending any content-type. So how would the server know 
what sort of data you're sending?  By default, httpapi sets the 
content-type to text/xml -- but you must be overriding this by 
specifying blanks for the content-type parameter.  (Unless you changed 
it to blanks in config_h?) that's a weird thing to do.


> Is the 'not enough space' message coming from them?
>

Yes, the "not enough space" is coming from them.   I know there's a lot 
of extra "chatter" in the debug file (mainly because I find it 
convenient for debugging code to throw a bunch of diagnostics into this 
log).  But, if it helps, this is exactly what you are sending to them:


POST /AdminService/XmlServer.aspx 
    HTTP/1.1
Host: staging.surescripts.net
User-Agent: http-api/1.16
Expect: 100-continue
Content-Length: 876

(876 byte long XML document goes here -- excluded for brevity)


And this is what they are sending in response:

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Expires: Fri, 27 Jan 2012 00:03:04 GMT
Server: Microsoft-IIS/7.5
Set-Cookie: ASP.NET_SessionId=i3rigyr5vyznwu3qcc3tnbn3; path=/; HttpOnly
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Fri, 27 Jan 2012 16:43:03 GMT
Content-Length: 55
Set-Cookie: BIGipServerStaging=2333284780.20480.0000; path=/

Unknown error: There is not enough space on the disk.


In theory, the "200 OK" means that there were no errors.  But, at the 
very least, it does mean that the HTTP server on their end read in the 
876 bytes of XML.

Then, they sent back 55 bytes of data that's supposedly in "text/html" 
format.  (But it looks like plain text to me.)  Those 55 bytes contain 
the string "Unknown error: There is not enough space on the disk."

That error message is not especially useful, as I can't imagine that the 
876 bytes filled up their hard drive.

My best guess is that their application is asking the HTTP server to 
return the XML data, so it can process it. But, since you didn't tell 
the server that your data was XML (that's what content-type does) the 
server returns nothing.  This confuses the program, and somehow causes 
the spurious "Not enough space" error.

> PS: Yes, I know I have a wayyy old version of httpapi.  Have had zero
> issues and can't imaging that is causing this.

I don't see anything here that would've been solved by updating HTTPAPI. 
However, there are a whole bunch of issues that have been fixed since 
1.16 was released. If you suspect any of the problems are due to 
HTTPAPI, you'll need to update it before we'll be able to help.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------