Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If I had to guess?
You're trying to write into a forbidden location.
Why don't you tell us where you're trying to write the web page to because it looks like your trying to write to the html address you pulled the web page from. What are the permissions on the directory you're trying to FTP into ?
The location that I'm writing to is http://home.telfort.nl/chaos_and_order.com/
To prove that the location is not forbidden I can perform wput/wget operation to/from the specified location using my fedora machine which is not behind a proxy:
Code:
[boris@e6410dl ~]$ wput TestFile.ods ftp://user.name:secret@home.telfort.nl
--22:46:39-- `TestFile.ods'
=> ftp://user.name:xxxxx@213.205.34.110:21/TestFile.ods
Connecting to 213.205.34.110:21... connected!
Logging in as user.name ... Logged in!
Length: 26,296
97% [=========================================================================> ] 25,600
22:46:42 (TestFile.ods) - `42.82K/s' [26296]
FINISHED --22:46:42--
Transfered 26,296 bytes in 1 file at 8.35K/s
[boris@e6410dl ~]$ mv TestFile.ods TestFile.bak
[boris@e6410dl ~]$ wget ftp://user.name:secret@home.telfort.nl/TestFile.ods
--2014-06-21 22:47:19-- ftp://user.name:*password*@home.telfort.nl/TestFile.ods
=> \u2018TestFile.ods\u2019
Resolving home.telfort.nl (home.telfort.nl)... 213.205.34.110
Connecting to home.telfort.nl (home.telfort.nl)|213.205.34.110|:21... connected.
Logging in as user.name ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD not needed.
==> SIZE TestFile.ods ... 26296
==> PASV ... done. ==> RETR TestFile.ods ... done.
Length: 26296 (26K) (unauthoritative)
100%[==============================================================================>] 26,296 59.1KB/s in 0.4s
2014-06-21 22:47:22 (59.1 KB/s) - \u2018TestFile.ods\u2019 saved [26296]
[boris@e6410dl ~]$ diff TestFile.*
Files TestFile.bak and TestFile.ods are identical
[boris@e6410dl ~]$
By the way, when I leave out "--proxy=http" option, there is no "Proxy states 'HTTP/1.0 403 Forbidden"
Code:
user123@acc4012 $ wput TestFile.ods ftp://user.name:secret@home.telfort.nl
--23:15:05-- `TestFile.ods'
=> ftp://user.name:xxxxx@home.telfort.nl:21/TestFile.ods
Connecting to home.telfort.nl:21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Waiting 10 seconds... Connecting to :21... Error: recv() timed out. No data received
failed!
Which proxy server are you using?
These instructions pertain to squid.
Quote:
[root@server ~#]vi /etc/squid/squid.conf
acl SSL_ports port 443 21 #(Edit add the ftp port 21 to SSL port acl)
acl ftp proto FTP #(Create a new acl for ftp protocol)
http_access allow ftp #(Allow browsing above created ftp acl)
#save the squid.conf file
However I'd think most proxies are going to need something similar in their config setup. The "acl" calls on the SSL ports and ftp protocols would indicate that at least with Squid, without the configuration modification, you'd probably get a "forbidden" response.
I'm not able to change/configure the proxy. Proxy is being administrated by the company IT staff.
However if ncftp (see below) can connect to that location I suppose wput should also be able to do the same.
ncftp session:
Code:
user123@acc3066 ~ $ ncftp ftp://user.name:secret@home.telfort.nl
NcFTP 3.2.5 (Jan 10, 2011) by Mike Gleason (http://www.NcFTP.com/contact/).
Connecting to home.telfort.nl via this.is.confidential...
Ready.
Logging in...
User user.name logged in.
Quotas on: using 30123.10 of 51200.00 kb
Logged in to home.telfort.nl.
Current remote directory is /.
ncftp / > ll
drwxrwxrwx 2 user.name@telfort.nl storegrp 4096 Jan 10 2008 cgi-art
drwxr-xr-x 12 user.name@telfort.nl storegrp 4096 Jun 15 21:24 Fedora
drwxr-xr-x 2 user.name@telfort.nl storegrp 4096 Oct 31 2008 octave
drwxr-xr-x 9 user.name@telfort.nl storegrp 4096 Aug 28 2010 openSuSE
drwxr-xr-x 2 user.name@telfort.nl storegrp 4096 Apr 26 16:11 Ubuntu
drwxr-xr-x 2 user.name@telfort.nl storegrp 4096 Dec 27 2012 Windows
ncftp / > exit
user123@acc3066 ~ $
This is my proxy configuration for ncftp:
Code:
# NcFTP firewall preferences
# ==========================
#
# If you need to use a proxy for FTP, you can configure it below.
# If you do not need one, leave the ``firewall-type'' variable set
# to 0. Any line that does not begin with the ``#'' character is
# considered a configuration command line.
#
# NOTE: NcFTP does NOT support HTTP proxies that do FTP, such as "squid"
# or Netscape Proxy Server. Why? Because you have to communicate with
# them using HTTP, and this is a FTP only program.
#
# Types of firewalls:
# ------------------
#
# type 1: Connect to firewall host, but send "USER user@real.host.name"
#
# type 2: Connect to firewall, login with "USER fwuser" and
# "PASS fwpassword", and then "USER user@real.host.name"
#
# type 3: Connect to and login to firewall, and then use
# "SITE real.host.name", followed by the regular USER and PASS.
#
# type 4: Connect to and login to firewall, and then use
# "OPEN real.host.name", followed by the regular USER and PASS.
#
# type 5: Connect to firewall host, but send
# "USER user@fwuser@real.host.name" and
# "PASS pass@fwpass" to login.
#
# type 6: Connect to firewall host, but send
# "USER fwuser@real.host.name" and
# "PASS fwpass" followed by a regular
# "USER user" and
# "PASS pass" to complete the login.
#
# type 7: Connect to firewall host, but send
# "USER user@real.host.name fwuser" and
# "PASS pass" followed by
# "ACCT fwpass" to complete the login.
#
# type 8: Connect to firewall host, but send "USER user@real.host.name:port"
#
# type 9: Connect to firewall host, but send "USER user@real.host.name port"
#
# type 0: Do NOT use a firewall (most users will choose this).
#
firewall-type=1
#
#
#
# The ``firewall-host'' variable should be the IP address or hostname of
# your firewall server machine.
#
firewall-host=this.is.confidential
#
#
#
# The ``firewall-user'' variable tells NcFTP what to use as the user ID
# when it logs in to the firewall before connecting to the outside world.
#
#firewall-user=user123
#
#
#
# The ``firewall-password'' variable is the password associated with
# the firewall-user ID. If you set this here, be sure to change the
# permissions on this file so that no one (except the superuser) can
# see your password. You may also leave this commented out, and then
# NcFTP will prompt you each time for the password.
#
#firewall-password=fwpass
#
#
#
# Your firewall may require you to connect to a non-standard port for
# outside FTP services, instead of the internet standard port number (21).
#
firewall-port=21
#
#
#
# You probably do not want to FTP to the firewall for hosts on your own
# domain. You can set ``firewall-exception-list'' to a list of domains
# or hosts where the firewall should not be used. For example, if your
# domain was ``probe.net'' you could set this to ``.probe.net''.
#
# If you leave this commented out, the default behavior is to attempt to
# lookup the current domain, and exclude hosts for it. Otherwise, set it
# to a list of comma-delimited domains or hostnames. The special token
# ``localdomain'' is used for unqualified hostnames, so if you want hosts
# without explicit domain names to avoid the firewall, be sure to include
# that in your list.
#
firewall-exception-list=localhost,localdomain
#
#
#
# You may also specify passive mode here. Normally this is set in the
# regular $HOME/.ncftp/prefs file. This must be set to one of
# "on", "off", or "optional", which mean always use PASV,
# always use PORT, and try PASV then PORT, respectively.
#
#passive=on
#
#
#
# NOTE: This file was created for you on Thu Jun 19 21:50:59 2014
# by NcFTP 3.2.5. Removing this file will cause the next run of NcFTP
# to generate a new one, possibly with more configurable options.
#
# ALSO: A /usr/local/etc/ncftp.firewall file, if present, is processed before this file,
# and a /usr/local/etc/ncftp.firewall.fixed file, if present, is processed after.
Last edited by blnl; 06-22-2014 at 09:41 AM.
Reason: improve explanation
Yes, I opened a support ticket.
First line of support does not have the knowledge to give a useful advice, while this is not high enough priority to get to the second line of support.
blnl, I'm going to refer you back to post #2, you are trying to write to a forbidden location. I'm not going to tell you how to bypass your corporate proxy server, other than to suggest that if you have a cell phone that you can hook to your laptop and get internet that way... as long as it's OK with them that would fix your problem AND has the added advantage of not getting you fired for being a pernicious threat to domain security.
blnl, I'm going to refer you back to post #2, you are trying to write to a forbidden location. I'm not going to tell you how to bypass your corporate proxy server, other than to suggest that if you have a cell phone that you can hook to your laptop and get internet that way... as long as it's OK with them that would fix your problem AND has the added advantage of not getting you fired for being a pernicious threat to domain security.
There is no reason to be concerned about my job security
Firstly, I'm not trying to bypass the proxy server. I need a solution that does not violate the security. Secondly, it is in fact the IT department that advised me to try out wget and wput as means to exchange large files with the supplier ftp account. For some reason ,unknown to me, after upgrading our server farm to RHEL 6, there is neither ftp nor gftp available on new servers. We only have a few RHEL 5 machines left that still have the ftp capability (but these machines are going to be decommissioned any time soon). Finally, I already have found a working solution (ncftp) to exchange files with supplier (as it would be inappropriate to use supplier account for testing, I'm using my private ftp account instead). ncftp works fine with corporate proxy as I demonstrated earlier in this thread. Getting the wput working is out of pure curiosity (not the necessity)
It seams that wput is not complementary to wget, as wget can connect trough proxy and wput cannot. I'll try posting this question at wput support...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Need help with wput (proxy configuration)
