Re: squid with mysql support
Hi.I'm sorry .I post an empty message by mistake. I add mysql support to squid-2,6.stable13. It's working normally.now it's possible to log some entries from access.log (timestamp,auth-user,ip,query size) directly into mysql database which connection parameters can be changed from squid.conf. if it's interesting for you,i can post all the sources as soon as possible. Thanks. -- View this message in context: http://www.nabble.com/squid-with-mysql-support-tf4796084.html#a13722029 Sent from the Squid - Development mailing list archive at Nabble.com.
Re: squid with mysql support
On Tue, Nov 13, 2007, Arthur Tumanyan wrote: I add mysql support to squid-2,6.stable13. It's working normally.now it's possible to log some entries from access.log (timestamp,auth-user,ip,query size) directly into mysql database which connection parameters can be changed from squid.conf. if it's interesting for you,i can post all the sources as soon as possible. Thanks. Yes please! Adrian -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
Re: [icap] if reqmod 204 - no respmod is sent by squid ?
On 11/12/07, Alex Rousskov [EMAIL PROTECTED] wrote: Squid should do a RESPMOD if it is configured to do a RESPMOD and the response from the server matches the corresponding ACL. This logic is unrelated to REQMOD, except in request satisfaction cases (but you are not doing request satisfaction above). If you believe this is a bug, please file a bug report and attach a cache.log with full debugging turned on during the entire buggy HTTP transaction (debug_options ALL,9). Thank you, Alex. Hello my pb is solved the reason was only that squid had been caching the first respmod ! ;-))) Y
Re: [squid-users] Solaris/OpenSSL/MD5 Issues
The patches to make MD5 work on Solaris have broken things on FreeBSD (at least) which also has a sys/md5.h. Compile fails with error: `MD5_DIGEST_LENGTH' was not declared in this scope It seems to me that the original problem was just that Squid's own MD5 routines are using names that collide with some system libraries/headers. Since we already ship a public domain MD5 implementaiton with Squid, why not just change our names to be unique and then always use them? Why go through this yucky configure maybe-find-some-libraries-here or maybe-find-them-there stuff? DW
Re: [squid-users] Solaris/OpenSSL/MD5 Issues
The patches to make MD5 work on Solaris have broken things on FreeBSD (at least) which also has a sys/md5.h. Compile fails with error: `MD5_DIGEST_LENGTH' was not declared in this scope It seems to me that the original problem was just that Squid's own MD5 routines are using names that collide with some system libraries/headers. Since we already ship a public domain MD5 implementaiton with Squid, why not just change our names to be unique and then always use them? Why go through this yucky configure maybe-find-some-libraries-here or maybe-find-them-there stuff? DW Well, for starters its not as messy as it seems, it replaces a whole bunch of configure.in if-else clauses with a single pre-compiler #if-else in the header where it is actually needed anyway. There it produces the 'nice' defined names/variables squid can use and it reduces the maintenance workload on all of us keeping that code up to date. If the OS or another project are doing all the work maintaining it, why duplicate the problems and fixes ourselves? As for making squid use unique names. That is the general idea. I think in most cases squid uses x... and has a lib/*.h which does the use A or use B, #define whichever to be x... for squid to use. The small problem here is that this case squid is not yet using xMD5*, but trying to do it to one of the optional standard naming schemes. The bigger problem which you have just uncovered is that FreeBSD does provide a sys/md5.h, but does not define the MD5_DIGEST_CHARS or MD5_DIGEST_ For the fix of FreeBSD. It should just be a little tweak of the #define for What I'm thinking to do now (bigger change than I wanted to make) to get around the FreeBSD case is add that 'x' at the front of these MD5 functions within all squid code. And update the md5.h header to only use the OS ones if they define MD5_DIGEST_LENGTH properly to the size we apparently need it. src/CacheDigest.cc has an assert(MD5_DIGEST_CHARS==16) with a note about hash keys. If anyone can think of a way of picking openssl without the USE_OPENSSL logics migrating in from configure.in, please mention. Might be worth getting done for the 3.1 cleanup. Amos
Re: cvs commit: squid3/src cache_cf.cc
rousskov2007/11/13 16:06:01 MST Modified files: src cache_cf.cc Log: Returning -1 in the unreached portion of u_short GetService() code results in a type conversion warning. Doh. Sorry. I thought I caught all of those. Amos
Re: [squid-users] Solaris/OpenSSL/MD5 Issues
How does this attached patch work for both of you? Amos MD5-freebsd.patch Description: Binary data
