Should we keep the man pages?

2009-02-09 Thread Per Andreas Buer
Hi,

There is a lot of confusion regarding the documentation. Some of it is
in the wiki and some of it is in the manual. Some of it is missing - but
as always, we're working on that. :-)

Should we drop the man pages? Should we drop all of them or just man
vcl? Dropping a man page would men we would incorporate the content
into the wiki - maybe adding a few extra ACL's on the pages to restrict
editing.

___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Should we keep the man pages?

2009-02-09 Thread Poul-Henning Kamp
In message 498fede4.7060...@redpill-linpro.com, Per Andreas Buer writes:
Hi,

There is a lot of confusion regarding the documentation. Some of it is
in the wiki and some of it is in the manual. Some of it is missing - but
as always, we're working on that. :-)

Should we drop the man pages? Should we drop all of them or just man
vcl? Dropping a man page would men we would incorporate the content
into the wiki - maybe adding a few extra ACL's on the pages to restrict
editing.

I think there should be a manpage for the executables, varnishd, varnishlog,
varnishstat etc.

But for documenting the overall workings and VCL in particular, manpages
suffer badly from the inability to include sensible illustrations.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Should we keep the man pages?

2009-02-09 Thread Justin Finkelstein
I agree; man pages are normally used (in my experience) to describe how
to access program control instructions, such as parameters, description
and exit codes.

I think the best approach would be this split, with a static html (or
other format) of the wiki documentation included in the distributable
archive.

On Mon, 2009-02-09 at 08:50 +, Poul-Henning Kamp wrote:

 In message 498fede4.7060...@redpill-linpro.com, Per Andreas Buer writes:
 Hi,
 
 There is a lot of confusion regarding the documentation. Some of it is
 in the wiki and some of it is in the manual. Some of it is missing - but
 as always, we're working on that. :-)
 
 Should we drop the man pages? Should we drop all of them or just man
 vcl? Dropping a man page would men we would incorporate the content
 into the wiki - maybe adding a few extra ACL's on the pages to restrict
 editing.
 
 I think there should be a manpage for the executables, varnishd, varnishlog,
 varnishstat etc.
 
 But for documenting the overall workings and VCL in particular, manpages
 suffer badly from the inability to include sensible illustrations.
 


___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Configuration question about a domain list for a http.req.host comparaison

2009-02-09 Thread Damien Desmarets
Hello,
I have 1 question for you. I haven't found the response in the
documentation/wiki. I think you have a big job to wrtie a good
documentation ... the current is really poor !

So the question.
I have a list of differents domains:
azeazeaze.com
eruigeiogr.com
zezeirjiorf.com
...

My configuration file is actually like this:
if (req.http.host ~
^(azeazeaze.com|eruigeiogr.com|zezeirjiorf.com|...)$) {
set req.backend = principal_delivery;
} elsif (req.http.host ~
^(aazeazeazeaze.com|azeiazjeaioze.com|azejoazjeaiozejoaz.com|...)$) {
set req.backend = pictures_delivery;
} else {
error 403 Not supported
}

The regex comparison is very big with maybe 100 domains. It's not clear
inside my file, and difficult to made change.
Is it possible to include those domains in a list and match this list to
the req.http.host. Like this maybe:

#define DOMAINS_PRINCIPAL_LIST domains_principal_list.txt
#define DOMAINS_PICTURES_LIST domains_pictures_list.txt

if (req.http.host ~ DOMAINS_PINCIPAL_LIST) {
set req.backend = principal_delivery;
} elsif (req.http.host ~ DOMAINS_PICTURES_LIST) {
set req.backend = pictures_delivery;
} else {
error 403 Not supported
}

I know the constant don't contain regex valid content but it's a
pseudo-code to show you the idea.

And my file domains_principal_list.txt contains for exemple:
azeazeaze.com
eruigeiogr.com
zezeirjiorf.com

Is it possible to do this in VCL origin configuration?

Thank for your help.

Regards,
Damien Desmarets

___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Weird log entries

2009-02-09 Thread Alecs Henry
Hi guys,

I was wondering if any of you has seen the following log entries when using
varnishncsa:
127.0.0.1 - - [00/Jan/1900:00:00:00 +] (null) (null) (null) (null) -
- -

Those are coupled with:
127.0.0.1 - - [09/Feb/2009:19:39:46 +] (null) (null) (null) 200 39678
- -
I can see an object in the page that has that size (image) -- through
firebug, but the object didn't load into the browser until I hit reload.

And there are also many entries like the following:
127.0.0.1 - - [09/Feb/2009:19:39:52 +] GET
http://www.example.com/img/mod.gif HTTP/1.1 200 951 
http://www.example.com/style.css; Mozilla/5.0 (X11; U; Linux x86_64; en;
rv:1.9.0.5) Gecko/2008121623 Ubuntu/8.10 (intrepid) Firefox/3.0.5

These entries are from communication with the backend server

I expected it to show the backend name instead of 127.0.0.1.

Is there an explanation?

Thanks!

Alecs
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Weird log entries

2009-02-09 Thread Nick Loman
Alecs Henry wrote:

 Those are coupled with:
 127.0.0.1 - - [09/Feb/2009:19:39:46 +] (null) (null) (null) 200 
 39678 - -
 I can see an object in the page that has that size (image) -- through 
 firebug, but the object didn't load into the browser until I hit reload.

I've seen log entries like this for HTTP 1.0 requests (using Varnish 
1.2), as that version of Varnish did not have support for parsing HTTP 
1.0 headers.

Cheers,

Nick.



___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Weird log entries

2009-02-09 Thread Alecs Henry
Hi Nick,

I forgot to say... It's varnish-trunk.
But I saw it on both varnish 2.0.1 and 2.0.2.

Alecs

On Mon, Feb 9, 2009 at 6:20 PM, Nick Loman n...@loman.net wrote:

 Alecs Henry wrote:

  Those are coupled with:
 127.0.0.1 - - [09/Feb/2009:19:39:46 +] (null) (null) (null) 200
 39678 - -
 I can see an object in the page that has that size (image) -- through
 firebug, but the object didn't load into the browser until I hit reload.


 I've seen log entries like this for HTTP 1.0 requests (using Varnish 1.2),
 as that version of Varnish did not have support for parsing HTTP 1.0
 headers.

 Cheers,

 Nick.




___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Should we keep the man pages?

2009-02-09 Thread Per Andreas Buer

- Poul-Henning Kamp p...@phk.freebsd.dk wrote:

 In message 498fede4.7060...@redpill-linpro.com, Per Andreas Buer
 I think there should be a manpage for the executables, varnishd,
 varnishlog, varnishstat etc.
 
 But for documenting the overall workings and VCL in particular,
 manpages suffer badly from the inability to include sensible illustrations.

Ok. The first step is done. The content of man vcl now resides in the wiki. 

http://varnish.projects.linpro.no/wiki/VCL - feedback is welcome. As of now, 
there are no special restrictions on editing this page. 

-- 

Redpill Linpro - Changing the Game
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc