Hi,

Unfortunately, there is no way to set authentication parameters for proxy
servers on the command line. The settings http[s].proxyUser and
http[s].proxyPassword do not work. They're actually an "urban legend" -
these properties were never respected by Sun's JDK.

The reason why the proxy works in Eclipse is because at some point it
probably prompted you for your authentication credentials after you hit
"Deploy". Once you enter them once, the credentials are saved and re-used by
the JDK.

I'll file a bug for this issue. The ideal solution would be for the user to
be able to pass in the proxy username and proxy passwords as command-line
args to appcfg.

There is a potential workaround, but it is pretty ugly. What you would need
to do is write a new main class, and in that main class, you would register
a default 
Authenticator<http://java.sun.com/j2se/1.5.0/docs/api/java/net/Authenticator.html>with
your proxy username and password.
Then, you would call AppCfg.main, passing as args the same exact args that
were passed in to your main class. Of course, you'd then modify the appcfg
script to invoke your class instead of AppCfg.

As an FYI, if you want to set the http[s] proxy server and port, you can now
do this via the command line if you're using version 1.2.1 of the App Engine
SDK - you'll no longer need to edit the appcfg script and add
-Dhttp[s].proxy... Run the appcfg script with the -h option for more
information on the proxy options.


Rajeev



On Thu, May 21, 2009 at 5:18 PM, Rajeev Dayal <[email protected]> wrote:

> Hi,
>
> With regard to the proxy issue, I'll have to do some experimentation
> locally to see if there is actually a way to pass the username and password
> for an authentication-requiring proxy via the command line. I'll post back
> on this thread with my results shortly.
>
>
> Thanks,
> Rajeev
>
> 2009/5/21 Miguel Méndez <[email protected]>
>
>  Let's split this issue into two.  First, you want to be able to configure
>> the proxy settings.  I'll have one of our guys who knows the proxy issues
>> pretty well follow up on this thread.
>> Second, the compile button is not working?  Could you provide more details
>> as to how it fails?  Is there a stack trace?
>>
>> On Thu, May 21, 2009 at 10:05 AM, [email protected] <
>> [email protected]> wrote:
>>
>>>
>>> I still need to know how to configure, command line proxy settings
>>>
>>>
>>> !!! once again the new release of the plugin does not offer any
>>> solution to my problem
>>>
>>> the compile button is still not compiling even if I specify -Xss8m
>>> where as it worked and compile successfully from hosted mode with the
>>> same lower stack parameter (just -Xss1024k)
>>>
>>>
>>>
>>>
>>> On 21 mai, 13:25, "[email protected]" <[email protected]>
>>> wrote:
>>> > concerning the second case , it was a type mistake
>>> > my proxy requires authentiification and that's whay I mentionned the
>>> > second case
>>> >
>>> > -Dhttp.proxyUser=me
>>> > -Dhttp.proxyPassword=me_crypted                 ____instead of
>>> > proxyHost____
>>> >
>>> > when adding these two params I got my self in the second case
>>> >
>>> > , concerning your question for eclipse setting , I configured eclipse
>>> > to use the proxy with the same ,
>>> >
>>> > for every body this is a tip that may help , I changed the VM type in
>>> > jvm.cfg as -server (jvm ) that was helpful for some cases but not all
>>> > the time coz I still have stack overflow problems with bigger project
>>> > ( IE: if the code source of the project stay the same and I just
>>> > include more image ressources to the war directory the I got into
>>> > StackOverflow)
>>>
>>>
>>
>>
>> --
>> Miguel
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to