Dear Dave Borowitz,

thanks for your quick hint! I've solved the issue now:

My password in .netrc *was* correct, but I was missing the keyword 'password' in front of it. So obviously, I was not passing any password to the server. It's a pity such an omission is not apparent from the curl logs.

I am now able to clone and push with both option 1 (both clone and push worked before) and option 2 (corrected .netrc).

Thanks,
  Ondrej.

On 08/17/2011 07:40 PM, Dave Borowitz wrote:
I have just realized that we do not check username/password at all for
requests that only require anonymous access, which would explain why clones
and pulls work but pushes do not. (This was a conscious choice at the time
because that's how Subversion does authentication, but we are now
reconsidering it.)

The only other issue I can think of offhand is to make sure you're using
your Google-Code-only randomly-generated password from
https://code.google.com/hosting/settings.

On Wed, Aug 17, 2011 at 00:51, Ondřej Bojar<[email protected]>  wrote:

And one more bit of observation: yes, option 1 (access with the
password) works for me.


Are you able to push with option 1, or just clone (see above)?


O.

On Aug 16, 9:39 pm, Ondřej Bojar<[email protected]>  wrote:
Hi,

I've got the same problem (clone works, push does not) with a slightly
older git client. My trace is fairly similar:

...>  GET /p/ondrej-test-project-1//info/refs HTTP/1.1

Authorization: Basic b25kcm...LmNvbTo=
User-Agent: git/1.7.0.4
Host: code.google.com
Accept: */*
Pragma: no-cache

* The requested URL returned error: 403
* Closing connection #0
error: The requested URL returned error: 403 while accessinghttps://
code.google.com/p/ondrej-test-project-1//info/refs

I will try if at least the password-based access works.

Any suggestion appreciated but I'm tempted to believe the reason is
somewhere on the server side.

Thanks, Ondrej.

On Aug 15, 9:48 pm, Oliver<[email protected]>  wrote:

Thanks for looking into this. .netrc is properly configured, clone is
fine,
only push has problems.
the trace log is attached.

error: The requested URL returned error: 403 while accessinghttps://
code.google.com/p/scigest/info/refs

fatal: HTTP request failed
panda:~/scigest[master]$ GIT_CURL_VERBOSE=1 git push
* About to connect() to code.google.com port 443 (#0)
*   Trying 74.125.67.100... * Connected to code.google.com(74.125.67.100)
port 443 (#0)
* SSL connection using RC4-SHA
* Server certificate:
*  subject: C=US; ST=California; L=Mountain View; O=Google Inc;
CN=*.google.com
*  start date: 2011-07-27 10:11:59 GMT
*  expire date: 2012-07-27 10:21:59 GMT
*  subjectAltName: code.google.com matched
*  issuer: C=US; O=Google Inc; CN=Google Internet Authority
*  SSL certificate verify ok.>  GET
/p/scigest/info/refs?service=git-receive-pack HTTP/1.1

User-Agent: git/1.7.5.3
Host: code.google.com
Accept: */*
Pragma: no-cache

<  HTTP/1.1 401 Unauthorized
<  WWW-Authenticate: Basic realm="Google Code git Repository"
<  Content-Type: text/html; charset=UTF-8
<  X-Content-Type-Options: nosniff
<  Date: Mon, 15 Aug 2011 22:17:27 GMT
<  Server: git_frontend
<  Content-Length: 11846
<  X-XSS-Protection: 1; mode=block
<
* Ignoring the response-body
* Connection #0 to host code.google.com left intact
* Issue another request to this URL:
'https://code.google.com/p/scigest/info/refs?service=git-receive-pack'
* Re-using existing connection! (#0) with host code.google.com
* Connected to code.google.com (74.125.67.100) port 443 (#0)
* Server auth using Basic with user 'my email address'>  GET
/p/scigest/info/refs?service=git-receive-pack HTTP/1.1

Authorization: Basic ZndhbmcyQGdtYWlsLmNvbTo=
User-Agent: git/1.7.5.3
Host: code.google.com
Accept: */*
Pragma: no-cache

* The requested URL returned error: 403
* Closing connection #0
* About to connect() to code.google.com port 443 (#0)
*   Trying 74.125.67.100... * Connected to code.google.com(74.125.67.100)
port 443 (#0)
* SSL re-using session ID
* SSL connection using RC4-SHA
* Server certificate:
*  subject: C=US; ST=California; L=Mountain View; O=Google Inc;
CN=*.google.com
*  start date: 2011-07-27 10:11:59 GMT
*  expire date: 2012-07-27 10:21:59 GMT
*  subjectAltName: code.google.com matched
*  issuer: C=US; O=Google Inc; CN=Google Internet Authority
*  SSL certificate verify ok.
* Server auth using Basic with user 'my email address'>  GET
/p/scigest/info/refs HTTP/1.1

Authorization: Basic ZndhbmcyQGdtYWlsLmNvbTo=
User-Agent: git/1.7.5.3
Host: code.google.com
Accept: */*
Pragma: no-cache

* The requested URL returned error: 403
* Closing connection #0
error: The requested URL returned error: 403 while accessinghttps://
code.google.com/p/scigest/info/refs

fatal: HTTP request failed

--
You received this message because you are subscribed to the Google Groups
"Project Hosting on Google Code" 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-code-hosting?hl=en.




--
Ondrej Bojar (mailto:[email protected] / [email protected])
http://www.cuni.cz/~obo

--
You received this message because you are subscribed to the Google Groups "Project 
Hosting on Google Code" 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-code-hosting?hl=en.

Reply via email to