basic authentication varnish before squid

[angelo iannello]

Hi all,
i have configured varnish that caching for speed improvement all request
passed to a backend based on squid proxy.

lan = varnish = squid = internet

Squid have a basic authentication but the popup relative does not appear to
the client browser, squid says cache denied authentication.

If i use squid directly i have succesfull access on the popup and i can
authenticate on it.

It's possible that varnish not recognize this authentication?

do exist a workaround for solving this problem?

tnx

Angelo

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

VUG1 meeting resport

[Poul-Henning Kamp]

I thought I would drop you a short report on our Varnish User
Group meeting this monday and tuesday in London.

About a dozen people participated, filling the meeting room Canonical
Software kindly provided to us for free.

Obviously, my TODO list grew continuously during the meeting but
it was my impression that everybody got something out of the meeting,
but on that I will let people speak for themselves.

We talked about a lot of things, and the result is more or less a
sort of a roadmap, but I need to do some text-procesing before
I can give a coherent view of it.

My personal impression was that the user group format worked out
well, we are not a big enough community to do actual conferences yet.

I also think most of the knowledge that needs to be shared, are in
the brains of everybody else than me[1].

One of the action items were to get more VCL code up on the wiki,
both snippets and complete examples, so that Varnish users can learn
and find inspiration from each other.

We talked about frequency of these meetings, and I think the overall
consensus was no more than a couple of times every year.  There were
no clear consensus, if it would be a good idea to piggyback on
other conferences (FOSSDEM etc) to synergize travel and the end result
I think, was that whoever arranges the meeting gets to decide where
and when.

Next meeting will probably be in .NL in the feb-march time-frame.

See you there!

Poul-Henning

[1] I was the only on in the room who did not run Varnish :-)

-- 
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: Backend fail 503 Service Unavailable

[M L]

Thanks Paul
Oh yes my fault , my varnish server open files 1024 , i guess my problem
solved , thx a lot



Thanks

TW



On Wed, Sep 23, 2009 at 4:45 AM, pub crawler pubcrawler@gmail.comwrote:

 Well I might be a bit off on this, but 503's often involve ulimit
 ceiling maximums being hit and exceeded.

 ulimit -a

 What is that limit set at for open files?

 In our experience many high performance web related software products
 suffer from low open file limit. I've seen 256 in SunOS, 1024 in
 Ubuntu.  We bump our settings in startup scripts for key servers to
 8096.  We run on dedicated servers - so no resource contention with
 other users.

 -Paul

 On 9/22/09, M L m...@tinwong.com wrote:
  Hi list
 
 
  I love varnish and really want to use it :D  Any clue to fix my problem ,
 it
  come out alot backend fail ( i guess timeout problem )
 
  my setup
 
  1.Centos 5.3 64bit varnish / webserver
  2.nginx backend server (it run over 200+days 2Mil pv/day without any
 problem
   healthy hardware)
  3.varnish connect to nginx in same internal switchs  (3com 5500 Giga
 layer4)
  4.Tested different version nginx was same happen ( nginx-0.6.36 
  nginx-0.7.61)
  5.Tested 2 different hardware for varnish same happen
  6.Changed nginx different timeout same happen , if changed to keepalive 0
  will more backend fail
  7.When i changed vcl to director rr x50 times , it didnt show 503 Service
  Unavailable on client side but like 2-8 sec. lag  when then Backend fail
  number increase
 
 
  #start
 
  varnishd -p lru_interval=3600 -a 0.0.0.0:80 -T localhost:3500 -p
  client_http11=on -f vconf2 -s file,/usr/local/varnish/cache.bin,80G -h
  classic,59 -p listen_depth=4096 -p obj_workspace=32768 -p
  sess_workspace=32768 -p send_timeout=327 -p first_byte_timeout=300 -p
  connect_timeout=5 -p vcl_trace=on
 
 
 
  #varnishlog
 
140 ReqStart c 121.203.78.124 4755 1383283991
140 RxRequestc GET
140 RxURLc /thread-1131553-1-1.html
140 RxProtocol   c HTTP/1.1
140 RxHeader c Host: www.zoobar.com
140 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1;
  zh-TW; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14
140 RxHeader c Accept: image/png,image/*;q=0.8,*/*;q=0.5
140 RxHeader c Accept-Language: zh-tw,en-us;q=0.7,en;q=0.3
140 RxHeader c Accept-Encoding: gzip,deflate
140 RxHeader c Accept-Charset: Big5,utf-8;q=0.7,*;q=0.7
140 RxHeader c Keep-Alive: 300
140 RxHeader c Connection: keep-alive
140 RxHeader c Referer:
 http://www.zoobar.com/thread-1131553-1-1.html
140 RxHeader c Cookie: cdb_sid=Nf6FM3;
 
 cdb_oldtopics=D1131553D1131773D1129353D1129581D1130425D1131274D1121699D1122534D1122581D1124932D1125704D1126044D1126641D1126650D1127247D1128227D1128288D1128329D1128640D1129165D1129403D1130965D1131013D1131057D1131460D1131464D1131491D
140 VCL_call c recv
140 VCL_tracec 1 106.14
140 VCL_tracec 2 110.5
140 VCL_tracec 3 110.41
140 VCL_tracec 9 143.5
140 VCL_tracec 14 157.1
140 VCL_tracec 15 157.5
140 VCL_tracec 17 162.1
140 VCL_tracec 18 162.5
140 VCL_tracec 26 172.9
140 VCL_tracec 27 172.13
140 VCL_tracec 30 180.1
140 VCL_tracec 31 180.5
140 VCL_tracec 33 184.1
140 VCL_tracec 34 184.5
140 VCL_tracec 36 192.1
140 VCL_tracec 37 192.5
140 VCL_tracec 39 198.1
140 VCL_tracec 40 198.5
140 VCL_tracec 41 198.31
140 VCL_tracec 42 199.9
140 VCL_tracec 44 202.18
140 VCL_tracec 45 202.53
140 VCL_tracec 49 213.1
140 VCL_tracec 84 42.14
140 VCL_tracec 85 43.9
140 VCL_tracec 93 53.5
140 VCL_tracec 94 53.9
140 VCL_tracec 97 57.5
140 VCL_tracec 98 57.9
140 VCL_tracec 99 57.35
140 VCL_tracec 100 57.52
140 VCL_return   c pass
140 VCL_call c pass
140 VCL_tracec 103 74.14
140 VCL_return   c pass
140 VCL_call c error
140 VCL_tracec 124 129.15
140 VCL_return   c deliver
140 Length   c 466
140 VCL_call c deliver
140 VCL_tracec 69 327.17
140 VCL_tracec 70 328.21
140 VCL_tracec 75 344.1
140 VCL_tracec 120 110.17
140 VCL_return   c deliver
140 TxProtocol   c HTTP/1.1
140 TxStatus c 503
140 TxResponse   c Service Unavailable
140 TxHeader c Server: Varnish
140 TxHeader c Retry-After: 0
140 TxHeader c Content-Type: text/html; charset=utf-8
140 TxHeader c Content-Length: 466
140 TxHeader c Date: Tue, 22 Sep 2009 16:15:52 GMT
140 TxHeader c X-Varnish: 1383283991
140 TxHeader c Age: 0
140 TxHeader c Via: 1.1 varnish
140 TxHeader c Connection: close
140 ReqEnd   c 1383283991 1253636152.715658903 1253636152.715944052
  0.016985893 0.000265121 0.20027
140 SessionClose c error
140 StatSess c