Reporting Factors by wget works with Fedora but not Ubuntu

EdH · 2018-08-25, 21:47

Can anyone possibly tell me why I can report factors via wget using my Fedora machine, but my Ubuntu machine doesn't work, even though it connects (or, at least, says it does)?

Ubuntu:

Code:

wget http://factordb.com/report.php?report=18463244954953084425120999474843941194888392281226674207422389138539733496611484745520706024226475442435016774348102117119203862148874337%3D2214764264865802436901049651014426845764380719047822370526717106213764982645367695201*52346726936111131202461*159254235693977964427502344117 -O dbRsave
--2018-08-25 16:55:26--  http://factordb.com/report.php?report=18463244954953084425120999474843941194888392281226674207422389138539733496611484745520706024226475442435016774348102117119203862148874337%3D2214764264865802436901049651014426845764380719047822370526717106213764982645367695201*52346726936111131202461*159254235693977964427502344117
Resolving factordb.com (factordb.com)... 138.201.37.196
Connecting to factordb.com (factordb.com)|138.201.37.196|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/html]
Saving to: ‘dbRsave’

dbRsave                 [ <=>                ]       0  --.-KB/s    in 0s      

2018-08-25 16:55:26 (0.00 B/s) - ‘dbRsave’ saved [0/0]

Fedora:

Code:

wget http://factordb.com/report.php?report=18463244954953084425120999474843941194888392281226674207422389138539733496611484745520706024226475442435016774348102117119203862148874337%3D2214764264865802436901049651014426845764380719047822370526717106213764982645367695201*52346726936111131202461*159254235693977964427502344117 -O dbRsave
--2018-08-25 17:18:50--  http://factordb.com/report.php?report=18463244954953084425120999474843941194888392281226674207422389138539733496611484745520706024226475442435016774348102117119203862148874337%3D2214764264865802436901049651014426845764380719047822370526717106213764982645367695201*52346726936111131202461*159254235693977964427502344117
Resolving factordb.com (factordb.com)... 138.201.37.196
Connecting to factordb.com (factordb.com)|138.201.37.196|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3248 (3.2K) [text/html]
Saving to: ‘dbRsave’

dbRsave             100%[===================>]   3.17K  --.-KB/s    in 0s      

2018-08-25 17:18:50 (93.5 MB/s) - ‘dbRsave’ saved [3248/3248]

Edit: A Debian machine on the same LAN works fine, but other Ubuntu machines do not work, either.

Thanks for any insights...

R. Gerbicz · 2018-08-25, 21:58

Why not use Google, the first hit:
https://stackoverflow.com/questions/...et-not-working

EdH · 2018-08-25, 22:39

Quote:

Originally Posted by R. Gerbicz

Why not use Google, the first hit:
https://stackoverflow.com/questions/...et-not-working

Thanks. I had not considered the troubles related, since I'm not getting any errors or forbidden messages. Also, I did not try using Firefox on the machine since I'm trying to get a script working.

DukeBG · 2018-08-27, 13:22

The resolved IP looks to be the same and if they're in the same LAN and we assume it does connect to the host (can you monitor that with some tool?), the only difference can be in HTTP headers sent with the request (such as User-Agent, although it should be the same in both cases Wget/version). You can try running wget with -d (or --debug) parameter to see if there'll be anything interesting in the debug information.

I also advise -C off (--cache=off), you don't want these requests to be cached. But it's unlikely to be a culprit, of course.

EdH · 2018-08-27, 16:37

Quote:

Originally Posted by DukeBG

The resolved IP looks to be the same and if they're in the same LAN and we assume it does connect to the host (can you monitor that with some tool?), the only difference can be in HTTP headers sent with the request (such as User-Agent, although it should be the same in both cases Wget/version). You can try running wget with -d (or --debug) parameter to see if there'll be anything interesting in the debug information.

I also advise -C off (--cache=off), you don't want these requests to be cached. But it's unlikely to be a culprit, of course.

Thanks for the reply. I followed the course in the first reply and it is working now. I might troubleshoot it further later on in the manner you suggest, but for now, it's running OK. Thanks again.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Someone is reporting orphan factors to FactorDB.	GP2	FactorDB	6	2018-07-24 19:45
Reporting small factors to PRP doesn't work	DukeBG	FactorDB	10	2018-05-02 11:16
Aliqueit/wget can't upload sequence (no data received). How to fix this?	Stargate38	FactorDB	2	2016-06-17 08:08
why works on m11846267	shahabmp	Information & Answers	4	2016-01-27 04:20
How it works?	kuratkull	Software	12	2007-03-16 13:40

2018-08-25, 21:58	#2
R. Gerbicz "Robert Gerbicz" Oct 2005 Hungary 2²×7×53 Posts	Why not use Google, the first hit: https://stackoverflow.com/questions/...et-not-working

2018-08-27, 13:22	#4
DukeBG Mar 2018 3·43 Posts	The resolved IP looks to be the same and if they're in the same LAN and we assume it does connect to the host (can you monitor that with some tool?), the only difference can be in HTTP headers sent with the request (such as User-Agent, although it should be the same in both cases Wget/version). You can try running wget with -d (or --debug) parameter to see if there'll be anything interesting in the debug information. I also advise -C off (--cache=off), you don't want these requests to be cached. But it's unlikely to be a culprit, of course.