Re: [Bug-wget] Read error (Success)?

[Tony Lewis]

First, I can assure you the server is NOT sending "Success"; anyway,
according to http.c, the bit between the parentheses comes from
hstat.rderrmsg. For the run that is described below the output file has a
size of 962378.

This is the only page on the server that has this problem and the exact same
page works fine when running the same code on another domain on the same
server. The configuration data that is being presented to the user differs
between the two servers, but whatever is causing it to fail is happening
after the configuration has been output.

In case it helps: WordPress runs the shutdown action including calling
wp_ob_end_flush_all from /wp-includes/functions.php.

I'll give you information as much as I can, but one must be logged into the
site as an administrator to access the page. I saved the cookies from the
last request in Chrome.

wget -dSv --load-cookies=cookies.txt --tries=1 --user-agent="Mozilla/5.0
(Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/70.0.3538.77 Safari/537.36"
"https://www.robertrudelic.com/wp-admin/options-general.php?page=exelana_kic
k_start_cart_settings_page&tab=exksc_tab_products" -O tab_products.html

And here is the output minus the cookies.

DEBUG output created by Wget 1.19.5 on darwin18.2.0.

--2018-11-20 10:57:22--
https://www.robertrudelic.com/wp-admin/options-general.php?page=exelana_kick
_start_cart_settings_page&tab=exksc_tab_products
Resolving www.robertrudelic.com (www.robertrudelic.com)... 23.229.205.103
Caching www.robertrudelic.com => 23.229.205.103
Connecting to www.robertrudelic.com
(www.robertrudelic.com)|23.229.205.103|:443... connected.
Created socket 6.
Releasing 0x00007f8a2b903950 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 6 to SSL handle 0x00007f8a2b9040f0
certificate:
  subject: CN=robertrudelic.com,OU=Domain Control Validated
  issuer:  CN=Go Daddy Secure Certificate Authority -
G2,OU=http://certs.godaddy.com/repository/,O=GoDaddy.com\\,
Inc.,L=Scottsdale,ST=Arizona,C=US
X509 certificate successfully verified and matches host
www.robertrudelic.com

---request begin---
GET
/wp-admin/options-general.php?page=exelana_kick_start_cart_settings_page&tab
=exksc_tab_products HTTP/1.1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
Accept: */*
Accept-Encoding: identity
Host: www.robertrudelic.com
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response... 
---response begin---
HTTP/1.1 200 OK
Date: Tue, 20 Nov 2018 18:57:23 GMT
Server: Apache
X-Powered-By: PHP/7.2.6
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
X-Frame-Options: SAMEORIGIN
Referrer-Policy: strict-origin-when-cross-origin
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=5
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

---response end---

  HTTP/1.1 200 OK
  Date: Tue, 20 Nov 2018 18:57:23 GMT
  Server: Apache
  X-Powered-By: PHP/7.2.6
  Expires: Wed, 11 Jan 1984 05:00:00 GMT
  Cache-Control: no-cache, must-revalidate, max-age=0
  X-Frame-Options: SAMEORIGIN
  Referrer-Policy: strict-origin-when-cross-origin
  Vary: Accept-Encoding,User-Agent
  Keep-Alive: timeout=5
  Connection: Keep-Alive
  Transfer-Encoding: chunked
  Content-Type: text/html; charset=UTF-8
Registered socket 6 for persistent reuse.
URI content encoding = 'UTF-8'
Length: unspecified [text/html]
Saving to: 'tab_products.html'

tab_products.html                    [    <=>
] 939.82K   923KB/s    in 1.0s    

Disabling further reuse of socket 6.
Closed 6/SSL 0x00007f8a2b9040f0
2018-11-20 10:57:29 (923 KB/s) - Read error at byte 962378 (Success).Giving
up.

-----Original Message-----
From: Dale R. Worley [mailto:address@hidden 
Sent: Tuesday, November 20, 2018 7:30 AM
To: Tony Lewis
Cc: address@hidden
Subject: Re: [Bug-wget] Read error (Success)?

"Tony Lewis" <address@hidden> writes:
> I'm getting the following error and don't understand what it's trying to
> tell me:
>
> Read error at byte 97430 (Success)
>
> What could the server be doing to cause wget to report an error with the
> details being "Success"?

My guess is that the server's response starts with a message including
the description "Success".

> For what it's worth, the page in question is coming from WordPress and the
> PHP script that's generating the page did in fact emit 97430 bytes of
data.
> Could the server be leaving the port in some weird state?

An easy way to help us is to report exactly the wget command line you
used, so we can replicate what you did and see what happens.  (As
opposed to now, when we're stuck making guesses as to what might have
happened.)

Dale