Application verification failure

Peter W A Wood peterwawood at gmail.com
Mon Mar 24 22:57:53 EDT 2014


Jacque

On 25 Mar 2014, at 10:29, J. Landman Gay wrote:

> On 3/24/14, 9:17 PM, Peter W A Wood wrote:
>> It's hard to tell whether the message is coming from your machine or
>> the server. Have you taken a look at the HTTP Headers? I believe you
>> can do that with libURLLastHTTPHeaders().
> 
> Do you know what I should be looking for? I'd like to record it only conditionally. There's a lot of server interaction going on, and logging all the headers would give me a gigantic log.

From the message, I would guess that the message is coming from either the C library that LiveCode uses for HTTP support or from the server. Looking at the HTTP responses might help you work out which of the two doesn't like the request.

In order to limit the number of entries in your log, I would suggest trying to look at any response that was not successful which usually means the Status 200 (though it can be anything in the 200 range and even some 300 codes may not indicate failure).  Do you know what HTTP Status code the server returns with a successful transaction?

Just in case it helps, here are the headers from a GET request to RunRev (with my annotations preceded by ##)

Schulz:Red-System-Libs peter$ curl -v http://runrev.com    ## a request send from curl from OS X terminal

### messages from Curl
* About to connect() to runrev.com port 80 (#0)
*   Trying 37.59.205.90... connected
* Connected to runrev.com (37.59.205.90) port 80 (#0)

### The headers curl sent to runrev, there is no body with a GET request
> GET / HTTP/1.1
> User-Agent: curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8y zlib/1.2.5
> Host: runrev.com
> Accept: */*
> 

### The response from RunRev
## Headers
< HTTP/1.1 200 OK
< Date: Tue, 25 Mar 2014 02:45:26 GMT
< Server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
< X-Powered-By: PHP/5.3.22
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
< X-Pingback: http://runrev.com/xmlrpc.php
< Set-Cookie: PHPSESSID=12ac26b4ddc9f94f4a5c8962f68ec5bb; path=/
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8
< 
## Body (The empty line is the boundary between headers and response. 
<!DOCTYPE html>
<!--[if lt IE 7]>      <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
<!--[if IE 7]>         <html class="no-js lt-ie9 lt-ie8"> <![endif]-->
<!
... and so on 


> The other bad part is that it only happens occasionally. I haven't seen it all day today, but over the weekend I had multiple instances.

Is the service more heavily used at the weekend?

Regards

Peter





More information about the use-livecode mailing list