Any ideas? On Aug 10, 11:39 am, Jon la Cour <j...@lacour.me> wrote: > I just copied all the headers and information that the login POSTs to / > session. I manually sent requests with the same headers to see what > response headers I would receive, there is no Set-Cookie header, but > this was logged into production.log for each request: "WARNING: > Invalid request host 'git.mydomain.com'. Session cookies will not > work" > > Here are the response headers as well: > > Date: Wed, 10 Aug 2011 17:29:56 GMT > Content-Encoding: gzip > Age: 0 > X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.8 > Status: 200 > X-Has-Flash: true > Connection: keep-alive > Content-Length: 1886 > X-UA-Compatible: IE=Edge,chrome=1 > X-Runtime: 13 > Via: 1.1 varnish > Server: nginx/1.0.5 > ETag: "646f566f0a31b08a6ff5a3526443bf42" > Vary: Accept-Encoding > X-Varnish: 1297057104 > Cache-Control: private, max-age=0, must-revalidate, max-age=0, public > Content-Type: text/html; charset=utf-8 > Accept-Ranges: bytes > Expires: Wed, 10 Aug 2011 17:29:56 GMT > > And here is my production configuration: > > cookie_secret: removed > repository_base_path: "/home/git/data/repositories" > extra_html_head_data: > system_message: > gitorious_client_port: 8001 > gitorious_client_host: git.mydomain.com > gitorious_host: git.mydomain.com > gitorious_user: git > exception_notification_emails: > mangle_email_addresses: true > public_mode: true > locale: en > archive_cache_dir: "/home/git/data/tarballs" > archive_work_dir: "/home/git/data/tarball-work" > only_site_admins_can_create_projects: true > hide_http_clone_urls: true > use_ssl: true > is_gitorious_dot_org: false > gitorious_support_email: s...@mydomain.com > > Thanks > > On Aug 10, 6:35 am, Marius Mårnes Mathiesen > > > > > > > > <marius.mathie...@gmail.com> wrote: > > On Tue, Aug 9, 2011 at 8:17 PM, Jon la Cour <j...@lacour.me> wrote: > > > > In the production.log file the only error is "The specified > > > gitorious_host is reserved in Gitorious". On the wiki it says that > > > Gitorious reserves git.* for git cloning. Would that at all effect the > > > login issue, or is it more something to do with cookies? > > > This sounds like a cookie issue. I assume you're accessing the site using > > whatever hostname is specified in gitorious.yml, right? One place to start > > is to check the Set-Cookie headers sent from your server (http and https, > > these need to be the same). You can do this either with a browser > > plugin/equivalent, or using curl. The Set-Cookie response header will > > contain a domain part which should match the hostname you're using - does > > it? > > > - Marius
-- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
