git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siju George <sgeorge.ml@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: XML Parsing Error: junk after document element
Date: Fri, 12 Feb 2010 09:53:06 +0530	[thread overview]
Message-ID: <b713df2c1002112023k757a54faq933b9a9bdacc7d1c@mail.gmail.com> (raw)
In-Reply-To: <m3ocjw82ai.fsf@localhost.localdomain>

Thanks a lot Jakub for the response :-)

On Thu, Feb 11, 2010 at 4:31 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>
> Which version of gitweb?[1]
>

 gitweb-1.6.0.6  - all packages are from pkgsrc on DragonFly BSD
v2.5.1.672.gf81ef-DEVELOPMENT #17: Tue Feb

> Which version of git?[2]
>

scmgit-1.6.6.1

>What web server?
>

 apache-2.2.14nb1

> Which version of CGI.pm is used by web server?[3]
>

$CGI::revision = '$Id: CGI.pm,v 1.263 2009/02/11 16:56:37 lstein Exp $';
$CGI::VERSION='3.43';




> Try to view source, or use different web browser that doesn't do
> strict XML validation to find the source of this error.
>

I was using firefox 3.6-2.
Trying with Konqueror Version 4.3.4 (KDE 4.3.4) Using KDE 4.3.4 (KDE
4.3.4) I dont get the error but it does not list my projectts. I get
this message on the page.

=================================================

projects /


 404 - No projects found

OPMLTXT
OK
The requested URL /cgi-bin/gitweb.cgi was not found on this server.

======================================================

this page is shown when I take the URL

http://172.16.3.27/cgi-bin/gitweb.cgi

but I have the projectroot configure in gitweb.conf and there is a git
project in that location.

# cat /usr/pkg/etc/gitweb.conf | grep projectroot
our $projectroot = "/Backup1/Data/git-repositories";
# ls -l /Backup1/Data/git-repositories
total 0
drwxr-xr-x  1 root  wheel  0 Feb 11 10:40 systems-configuration
# ls -l /Backup1/Data/git-repositories/systems-configuration/.git/
total 0
-rwxr-x---  1 root  wheel  393 Feb 11 11:03 COMMIT_EDITMSG
-rwxr-x---  1 root  wheel   23 Feb 11 10:40 HEAD
-rwxr-x---  1 root  wheel   92 Feb 11 10:40 config
-rwxr-x---  1 root  wheel   73 Feb 11 10:40 description
drwxr-x---  1 root  wheel    0 Feb 11 10:40 hooks
-rwxr-x---  1 root  wheel  120 Feb 11 11:29 index
drwxr-x---  1 root  wheel    0 Feb 11 10:40 info
drwxr-x---  1 root  wheel    0 Feb 11 10:58 logs
drwxr-x---  1 root  wheel    0 Feb 11 11:03 objects
drwxr-x---  1 root  wheel    0 Feb 11 10:40 refs
#


> If everything else fals, you can always edit gitweb.cgi to comment out
> content-type negotiation, to always serve as text/html mimetype -
> which should torn off XML validation, as below:
>
>        my $content_type;
>        # require explicit support from the UA if we are to send the page as
>        # 'application/xhtml+xml', otherwise send it as plain old 'text/html'.
>        # we have to do this because MSIE sometimes globs '*/*', pretending to
>        # support xhtml+xml but choking when it gets what it asked for.
>        # Disable content-type negotiation when caching (use mimetype good for all).
>        #if (defined $cgi->http('HTTP_ACCEPT') &&
>        #    $cgi->http('HTTP_ACCEPT') =~ m/(,|;|\s|^)application\/xhtml\+xml(,|;|\s|$)/ &&
>        #    $cgi->Accept('application/xhtml+xml') != 0) {
>        #       $content_type = 'application/xhtml+xml';
>        #} else {
>                $content_type = 'text/html';
>        #}
>
>

yes I tried it and the first error disappears from firefor and now I
get the same error from konqueror in firefox too

What could be the trouble?

Thanks

--Siju

  reply	other threads:[~2010-02-12  4:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11  7:47 XML Parsing Error: junk after document element Siju George
2010-02-11 11:01 ` Jakub Narebski
2010-02-12  4:23   ` Siju George [this message]
2010-02-12 10:48     ` Jakub Narebski
2010-02-17  9:46       ` Siju George

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=b713df2c1002112023k757a54faq933b9a9bdacc7d1c@mail.gmail.com \
    --to=sgeorge.ml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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).