git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Alan Smith <alanrogersmith@gmail.com>
Cc: git@vger.kernel.org, pasky@suse.cz
Subject: Re: MKCOL fails, 403 error
Date: Sun, 3 Feb 2008 16:35:38 +0100	[thread overview]
Message-ID: <20080203153538.GA17980@glandium.org> (raw)
In-Reply-To: <eae1aef50802030732s7536dfacufd0aaf41974c85d6@mail.gmail.com>

On Sun, Feb 03, 2008 at 10:32:39AM -0500, Alan Smith wrote:
> Mike,
> 
> I do have access to the log at /var/logs/apache2/error_log. What
> should I be looking for?

For whatever error message shows up at the time corresponding to when
the MKCOL request was done. You can grep MKCOL in the access_log to find
out. That might help you understand why the MKCOL fails.

Mike

      reply	other threads:[~2008-02-03 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eae1aef50802030535u1402471fh182a230f3e0667ea@mail.gmail.com>
2008-02-03 13:39 ` MKCOL fails, 403 error Alan Smith
2008-02-03 14:31   ` Mike Hommey
2008-02-03 15:32     ` Alan Smith
2008-02-03 15:35       ` Mike Hommey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080203153538.GA17980@glandium.org \
    --to=mh@glandium.org \
    --cc=alanrogersmith@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).