hmm well i've been trying to debug this it's weird if thiers a 404 it traverses through out the next several requests example notice this request was ok directly to the image 1216254753.708 286 10.108.3.22 TCP_REFRESH_HIT/304 235 GET http://10.108.111.181/loginuat/images/header_rightcorner.jpg - FIRST_UP_PARENT/uatbox - Now notice i use the main url 1216254757.937 511 10.108.3.22 TCP_MISS/200 4171 GET http://10.108.111.181/loginuat/ - FIRST_UP_PARENT/uatbox text/html Images wont use the /loginuat/ like the rest? weird? 1216254758.290 185 10.108.3.22 TCP_MISS/404 752 GET http://10.108.111.181/images/header_rightcorner.jpg - FIRST_UP_PARENT/mybox text/html 1216254758.291 113 10.108.3.22 TCP_MISS/404 751 GET http://10.108.111.181/images/massinsectionlogo.gif - FIRST_UP_PARENT/mybox text/html css works fine in /css folder? and js too but just not images ? is this a bug On Wed, Jul 16, 2008 at 7:36 PM, jason bronson <jasonbronson@xxxxxxxxx> wrote: > Thanks that works and makes more sense ! > > > i ended up adding this line also to turn on accel mode just to make > this support list complete > http_port 80 accel defaultsite=10.108.111.181 > > > > On Wed, Jul 16, 2008 at 6:19 PM, Henrik Nordstrom > <henrik@xxxxxxxxxxxxxxxxxxx> wrote: >> ons 2008-07-16 klockan 17:31 -0400 skrev jason bronson: >> >>> So if i hit repairdata.php it goes to my uatbox >>> if i hit index.htm it goes to admin >>> if I hit just main url it goes to mybox >>> >>> What confuses me is the last line below >>> if i change the last line to say : >>> cache_peer_access mybox allow uat then it fails on mybox requests >> >>> if i change it back to deny its fine? what exactly does this mean and >>> do for that matter? somehow im guessing its related to denial of >>> anything other then uat ? if thats right then why wouldnt i state >>> deny uat, foo so it would denial of both? >> >> >>> acl foo urlpath_regex ^/index.htm >>> acl uat urlpath_regex ^/repairdata.php >>> >>> cache_peer_aocess uatbox allow uat >>> cache_peer_access admin allow foo >>> cache_peer_access mybox deny uat >> >> This isn't complete. >> >> The default for all is "allow" which means any of the peers may be user. >> >> By adding an allow rule you say that this peer may only be used for the >> allowed requests. >> >> By adding a deny rule you say that this peer may only be used if the >> request is not in the denied set. >> >> Which means that mybox is valid for anything except for uat, that is >> including the foo stuff which I assume you do not want to have sent that >> way.. >> >> >> If you combine both allow & deny on the same peer then the lines is read >> top down until a match is found. If no match is found for the peer the >> desision is the opposite of the last rule you have for that peer. >> >> >> I think the following is what you want: >> >> cache_peer_aocess uatbox allow uat >> cache_peer_access admin allow foo >> cache_peer_access mybox deny uat >> cache_peer_access mybox deny foo >> >> This sends uat to uatbox, foo to admin, and anything else (not uat and >> not foo) to mybox. >> >> Regards >> Henrik >> >> > > > > -- > Thanks > > Contact Information > > skype: jbronson_ny > yahoo: advancedonsite > aim: advancedonsite > msn: advancedonsite@xxxxxxxxxxx > phone: 518-791-2697 > home: 518-886-8012 > JasonBronson@xxxxxxxxx > Web Designer and Programmer > Computer Hardware Repair and More > -- Thanks Contact Information skype: jbronson_ny yahoo: advancedonsite aim: advancedonsite msn: advancedonsite@xxxxxxxxxxx phone: 518-791-2697 home: 518-886-8012 JasonBronson@xxxxxxxxx Web Designer and Programmer Computer Hardware Repair and More
