views:

81

answers:

1

I'm having problems uploading an app to the google-app-engine from my work place. I believe the problem is related to proxy, because I do not see the same problem when following the same procedure from home. (I do not specify HTTP_PROXY from home).

These are the commands I run (hostname replaced):

set HTTP_PROXY=http://proxy.myhostname.com:8080
set HTTPS_PROXY=http://proxy.myhostname.com:8080
appcfg.py --insecure update myappfolder

When running the commands I get prompted for email and password, as expected, but after that it immediately exits with this errormessage:

Error 302: --- begin server output ---
<HTML>
<HEAD>
<TITLE>Moved Temporarily</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Moved Temporarily</H1>
The document has moved <A HREF="https://www.google.com/accounts/ClientLogin"&gt;here&lt;/A&gt;.
</BODY>
</HTML>
--- end server output ---

Note: I added the --insecure option because else it gave a warning of missing ssl module.

Any idea how to solve or workaround this problem?

A: 

Below is the relevant section from the Google docs.

Using an HTTP Proxy

If you are running appcfg.py behind an HTTP proxy, you must tell appcfg.py the name of the proxy. To set an HTTP proxy for appcfg.py, set the http_proxy and https_proxy environment variables.

Using Windows (in Command Prompt):

set HTTP_PROXY=http://cache.mycompany.com:3128
set HTTPS_PROXY=http://cache.mycompany.com:3128
appcfg.py update myapp

Using the command line in Mac OS X (in Terminal) or Linux:

export http_proxy="http://cache.mycompany.com:3128"
appcfg.py update myapp

By default, appcfg.py uses HTTPS to communicate with App Engine. If you require that it use HTTP instead, you can turn off HTTPS with the --insecure option:

appcfg.py --insecure update myapp
Taylor Leese
The procedure you're referring to is the exact procedure I was following. Tried both with and without --insecure.
Oberon
No, the commands you have posted show that you're setting HTTP_PROXY twice. You should be setting HTTP_PROXY and also HTTPS_PROXY (they are different and this one has an S after HTTP). I have already posted this as comment to your original post.
@mrl33t You are certainly right about the misplaced S, thank you for pointing that out. Unfortunately the fix doesn't solve my initial problem, so I still get the 302 error message.
Oberon