How to avoid pre-moderation of my comments?
mod_cache:  how to determine its running
Hello Guest
  
  • Login
• Register…
• Start blog
  • Who, Where, When
• What can I do?
• What to Read?
  • Polls
• Avatars
• Interests
  • Cities and Countries
• Random blog
• Users search
  • Search
• Games
• Tests
• QAIX
  • Ñîîáùåñòâà
• Talxy Chat
• Horoscope
• Online
 
Çàðåãèñòðèðóéñÿ!

QAIX > Apache HTTP Server > mod_cache: how to determine its running 1 December 2004 19:12:58

  Recent blog posts: 
  Forums:   
  Discuss: 
  Recent forum topics: 
  Recent forum comments:
  Moderators:

mod_cache: how to determine its running

Sean T Allen 1 December 2004 19:12:58
 Basics:

Server version: Apache/2.0.52

Compiled in modules:
core.c
mod_access.c
mod_auth.c
mod_cache.c
mod_disk_cache.c
mod_mem_cache.c
mod_log_config.c
mod_env.c
mod_setenvif.c
mod_proxy.c
proxy_connect.c
proxy_ftp.c
proxy_http.c
mod_ssl.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_dir.c
mod_imap.c
mod_actions.c
mod_alias.c
mod_rewrite.c
mod_so.c

And lastly issue...

I am reverse proxying to an httpd server instance running on 127.0.0.1:8081
Have a mem_cache setup that doesnt seem to be working....

Here are some snippets:

CacheEnable mem /
CacheRoot /cache/toppik
CacheSize 5000000
CacheGcInterval 1
CacheLastModifiedFa­ctor 0.1
CacheDefaultExpire 3600
CacheMaxExpire 43200
CacheForceCompletio­n 60
#CacheIgnoreCacheCo­ntrol On
CacheIgnoreNoLastMo­d On
MCacheMaxObjectCoun­t 10000
MCacheMaxObjectSize­ 12800000
MCacheMinObjectSize­ 0
MCacheRemovalAlgori­thm LRU
MCacheSize 100000

There are some disk cache related things in there as I was playing
around with it during test.

and the mod-rewrite stuff that proceeds the cache entries in the config file

RewriteEngine On

# send all requests to www
RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]
RewriteCond %{HTTP_HOST} !^$
RewriteCond %{SERVER_PORT} ^443$
RewriteRule ^/(.*) https://www.toppik.­info/$1 [L,R]
RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]
RewriteCond %{HTTP_HOST} !^$
RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]
# tracking rewrite
RewriteCond %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%2/$2?%1&%­3
RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2
RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3
RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­
# dynamic rewrite
RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P]
RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P]
# admin rewrite
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L]
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2
[R,L]
RewriteRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P]
RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P]
# lid mapping rewrite
RewriteRule ^/s-[^/]*/(.*) /$1
# hit tracking rewrite
RewriteRule /ht.gif$ /images/ht.gif [QSA]
# awstats
RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P]
# static file rewrite
#RewriteRule /(server.*) /$1 [L]
RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]

Standard response header example:

Date: Sun, 21 Nov 2004 04:34:49 GMT
Server: thttpd/2.25b 29dec2003
Content-Type: text/html; charset=iso-8859-1
Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT
Accept-Ranges: bytes
Content-Length: 35484
Cache-Control: max-age=43200
Expires: Sun, 21 Nov 2004 16:34:49 GMT

Some where o where do I have this misconfigured?
Order that module compiled in?
Something esoteric in the setup?
Freaky rewrite rule getting in the way?

Your help greatly appreciated...

-Sean-







-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org
Add comment
Axel-Stéphane SMORGRAV 22 November 2004 11:02:45 permanent link ]
 To answer the question in the subject line, set the LogLevel to debug and look in the error log. That should enable you to determine whether a particular document is cached, and if it is not, determine the reason for that.

From the look of the response headers the document should be cached. You should also have a look at the request headers and make sure that there is no "Cache-Control: no-cache".

-ascs

-----Message d'origine-----
De : Sean T Allen [mailto:sean@usaherbals.com]
Envoyé : dimanche 21 novembre 2004 04:48
À : apachehelp
Objet : [users@httpd] mod_cache: how to determine its running


Basics:

Server version: Apache/2.0.52

Compiled in modules:
core.c
mod_access.c
mod_auth.c
mod_cache.c
mod_disk_cache.c
mod_mem_cache.c
mod_log_config.c
mod_env.c
mod_setenvif.c
mod_proxy.c
proxy_connect.c
proxy_ftp.c
proxy_http.c
mod_ssl.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_dir.c
mod_imap.c
mod_actions.c
mod_alias.c
mod_rewrite.c
mod_so.c

And lastly issue...

I am reverse proxying to an httpd server instance running on 127.0.0.1:8081 Have a mem_cache setup that doesnt seem to be working....

Here are some snippets:

CacheEnable mem /
CacheRoot /cache/toppik
CacheSize 5000000
CacheGcInterval 1
CacheLastModifiedFa­ctor 0.1
CacheDefaultExpire 3600
CacheMaxExpire 43200
CacheForceCompletio­n 60
#CacheIgnoreCacheCo­ntrol On
CacheIgnoreNoLastMo­d On
MCacheMaxObjectCoun­t 10000
MCacheMaxObjectSize­ 12800000
MCacheMinObjectSize­ 0
MCacheRemovalAlgori­thm LRU
MCacheSize 100000

There are some disk cache related things in there as I was playing
around with it during test.

and the mod-rewrite stuff that proceeds the cache entries in the config file

RewriteEngine On

# send all requests to www
RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]
RewriteCond %{HTTP_HOST} !^$
RewriteCond %{SERVER_PORT} ^443$
RewriteRule ^/(.*) https://www.toppik.­info/$1 [L,R]
RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]
RewriteCond %{HTTP_HOST} !^$
RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]
# tracking rewrite
RewriteCond %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%2/$2?%1&%­3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­ # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2
[R,L]
RewriteRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P] RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*) /$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P] # static file rewrite #RewriteRule /(server.*) /$1 [L] RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]

Standard response header example:

Date: Sun, 21 Nov 2004 04:34:49 GMT
Server: thttpd/2.25b 29dec2003
Content-Type: text/html; charset=iso-8859-1
Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT
Accept-Ranges: bytes
Content-Length: 35484
Cache-Control: max-age=43200
Expires: Sun, 21 Nov 2004 16:34:49 GMT

Some where o where do I have this misconfigured?
Order that module compiled in?
Something esoteric in the setup?
Freaky rewrite rule getting in the way?

Your help greatly appreciated...

-Sean-






-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


Add comment
Sean T Allen 22 November 2004 18:06:59 permanent link ]
 My question then becomes... what should i see in the logfile that would
indicate that a file is being served from
the cache. And why if a file was cached, would i see headers from the
server it was originally proxied from...

Axel-Stéphane SMORGRAV wrote:
To answer the question in the subject line, set the LogLevel to debug and look in the error log. That should enable you to determine whether a particular document is cached, and if it is not, determine the reason for that.>
From the look of the response headers the document should be cached. You should also have a look at the request headers and make sure that there is no "Cache-Control: no-cache".>
-ascs>
-----Message d'origine----->De : Sean T Allen [mailto:sean@usaherbals.com] >Envoyé : dimanche 21 novembre 2004 04:48>À : apachehelp>Objet : [users@httpd] mod_cache: how to determine its running>
Basics:>
Server version: Apache/2.0.52>
Compiled in modules:> core.c> mod_access.c> mod_auth.c> mod_cache.c> mod_disk_cache.c> mod_mem_cache.c> mod_log_config.c> mod_env.c> mod_setenvif.c> mod_proxy.c> proxy_connect.c> proxy_ftp.c> proxy_http.c> mod_ssl.c> prefork.c> http_core.c> mod_mime.c> mod_status.c> mod_autoindex.c> mod_dir.c> mod_imap.c> mod_actions.c> mod_alias.c> mod_rewrite.c> mod_so.c>
And lastly issue...>
I am reverse proxying to an httpd server instance running on 127.0.0.1:8081 Have a mem_cache setup that doesnt seem to be working....>
Here are some snippets:>
CacheEnable mem />CacheRoot /cache/toppik>Cache­Size 5000000>CacheGcInte­rval 1>CacheLastModified­Factor 0.1>CacheDefaultExp­ire 3600>CacheMaxExpire­ 43200>CacheForceCom­pletion 60>#CacheIgnoreCach­eControl On>CacheIgnoreNoLas­tMod On>MCacheMaxObjectC­ount 10000>MCacheMaxObje­ctSize 12800000>MCacheMinO­bjectSize 0>MCacheRemovalAlgo­rithm LRU>MCacheSize 100000>
There are some disk cache related things in there as I was playing >around with it during test.>
and the mod-rewrite stuff that proceeds the cache entries in the config file>
RewriteEngine On>
# send all requests to www>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>RewriteCond %{HTTP_HOST} !^$>RewriteCond %{SERVER_PORT} ^443$>RewriteRule ^/(.*) https://www.toppik.­info/$1 [L,R]>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>RewriteCond %{HTTP_HOST} !^$>RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]># tracking rewrite>RewriteCond­ %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%2/$2?%1&%­3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­ # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2 >[R,L]>RewriteRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P] RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*) /$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P] # static file rewrite #RewriteRule /(server.*) /$1 [L] RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]>
Standard response header example:>
Date: Sun, 21 Nov 2004 04:34:49 GMT>Server: thttpd/2.25b 29dec2003>Content-T­ype: text/html; charset=iso-8859-1>­Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT>Accept-Ranges: bytes>Content-Lengt­h: 35484>Cache-Control­: max-age=43200>Expir­es: Sun, 21 Nov 2004 16:34:49 GMT>
Some where o where do I have this misconfigured?>Orde­r that module compiled in?>Something esoteric in the setup?>Freaky rewrite rule getting in the way?>
Your help greatly appreciated...>
-Sean->
------------------­--------------------­--------------------­----------->The official User-To-User support forum of the Apache HTTP Server Project.>See <URL:http://httpd.a­pache.org/userslist.­html> for more info.>To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org> " from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg>For additional commands, e-mail: users-help@httpd.ap­ache.org>



-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org
Add comment
Axel-Stéphane SMORGRAV 22 November 2004 18:39:36 permanent link ]
 The headers are cached along with the document, and they are served by the cache.

As far as headers are concerned, in your case the back-end server is thttpd; if the document is served from your Apache cache I believe the Server header should read "Apache".

If you turn on debug, you'll figure out how to determine whether a file is cached, and whether it is server from cache, very easily. The debug output from the cache modules is very explicit.

-ascs

-----Message d'origine-----
De : Sean T Allen [mailto:sean@usaherbals.com]
Envoyé : lundi 22 novembre 2004 16:07
À : users@httpd.apache.­org
Objet : Re: [users@httpd] RE :mod_cache: how to determine its running


My question then becomes... what should i see in the logfile that would
indicate that a file is being served from
the cache. And why if a file was cached, would i see headers from the
server it was originally proxied from...

Axel-Stéphane SMORGRAV wrote:
To answer the question in the subject line, set the LogLevel to debug >and look in the error log. That should enable you to determine whether >a particular document is cached, and if it is not, determine the reason >for that.>
From the look of the response headers the document should be cached. >>You should also have a look at the request headers and make sure that >>there is no "Cache-Control: no-cache".>
-ascs>
-----Message d'origine----->De : Sean T Allen [mailto:sean@usaherbals.com]>Envoyé : dimanche 21 novembre 2004 04:48>À : apachehelp>Objet : [users@httpd] mod_cache: how to determine its running>
Basics:>
Server version: Apache/2.0.52>
Compiled in modules:> core.c> mod_access.c> mod_auth.c> mod_cache.c> mod_disk_cache.c> mod_mem_cache.c> mod_log_config.c> mod_env.c> mod_setenvif.c> mod_proxy.c> proxy_connect.c> proxy_ftp.c> proxy_http.c> mod_ssl.c> prefork.c> http_core.c> mod_mime.c> mod_status.c> mod_autoindex.c> mod_dir.c> mod_imap.c> mod_actions.c> mod_alias.c> mod_rewrite.c> mod_so.c>
And lastly issue...>
I am reverse proxying to an httpd server instance running on >127.0.0.1:8081 Have a mem_cache setup that doesnt seem to be >working....>
Here are some snippets:>
CacheEnable mem />CacheRoot /cache/toppik>Cache­Size 5000000>CacheGcInte­rval 1>CacheLastModified­Factor 0.1>CacheDefaultExp­ire 3600>CacheMaxExpire­ 43200>CacheForceCom­pletion 60>#CacheIgnoreCach­eControl On>CacheIgnoreNoLas­tMod On>MCacheMaxObjectC­ount 10000>MCacheMaxObje­ctSize 12800000>MCacheMinO­bjectSize 0>MCacheRemovalAlgo­rithm LRU>MCacheSize 100000>
There are some disk cache related things in there as I was playing>around with it during test.>
and the mod-rewrite stuff that proceeds the cache entries in the config >file>
RewriteEngine On>
# send all requests to www>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>RewriteCond %{HTTP_HOST} !^$>RewriteCond %{SERVER_PORT} ^443$>RewriteRule ^/(.*) https://www.toppik.­info/$1 [L,R]>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>RewriteCond %{HTTP_HOST} !^$>RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]># tracking rewrite>RewriteCond­ %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*) RewriteRule >^/s-([^/]+)/(.*) /s-$1&kw=%2/$2?%1&%­3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­ # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2>[R,L]>Re­writeRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P] RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*) /$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P] # static file rewrite #RewriteRule /(server.*) /$1 [L] RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]>
Standard response header example:>
Date: Sun, 21 Nov 2004 04:34:49 GMT>Server: thttpd/2.25b 29dec2003>Content-T­ype: text/html; charset=iso-8859-1>­Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT>Accept-Ranges: bytes>Content-Lengt­h: 35484>Cache-Control­: max-age=43200>Expir­es: Sun, 21 Nov 2004 16:34:49 GMT>
Some where o where do I have this misconfigured?>Orde­r that module compiled in?>Something esoteric in the setup?>Freaky rewrite rule getting in the way?>
Your help greatly appreciated...>
-Sean->
------------------­--------------------­--------------------­----------->The official User-To-User support forum of the Apache HTTP Server >Project. See <URL:http://httpd.a­pache.org/userslist.­html> for more >info. To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org> " from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg>For additional commands, e-mail: users-help@httpd.ap­ache.org>


-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


Add comment
Sean T Allen 22 November 2004 18:53:05 permanent link ]
 Well what i see for debug output is the content getting cached...
then nothing... only access log, no debug information and the
response header continues to read thttpd ( yet you'd think it'd see the
proxy debug output
but I don't ).

I am thoroughly stymied by now.

Axel-Stéphane SMORGRAV wrote:
The headers are cached along with the document, and they are served by the cache.>
As far as headers are concerned, in your case the back-end server is thttpd; if the document is served from your Apache cache I believe the Server header should read "Apache".>
If you turn on debug, you'll figure out how to determine whether a file is cached, and whether it is server from cache, very easily. The debug output from the cache modules is very explicit.>
-ascs>
-----Message d'origine----->De : Sean T Allen [mailto:sean@usaherbals.com] >Envoyé : lundi 22 novembre 2004 16:07>À : users@httpd.apache.­org>Objet : Re: [users@httpd] RE :mod_cache: how to determine its running>
My question then becomes... what should i see in the logfile that would >indicate that a file is being served from>the cache. And why if a file was cached, would i see headers from the >server it was originally proxied from...>
Axel-Stéphane SMORGRAV wrote:>
To answer the question in the subject line, set the LogLevel to debug >>and look in the error log. That should enable you to determine whether >>a particular document is cached, and if it is not, determine the reason >>for that.>>
From the look of the response headers the document should be cached. >>
You should also have a look at the request headers and make sure that >>>there is no "Cache-Control: no-cache".>>>
-ascs>>
-----Message d'origine----->>De : Sean T Allen [mailto:sean@usaherbals.com]>>Envoyé : dimanche 21 novembre 2004 04:48>>À : apachehelp>>Objet : [users@httpd] mod_cache: how to determine its running>>
Basics:>>
Server version: Apache/2.0.52>>
Compiled in modules:>> core.c>> mod_access.c>> mod_auth.c>> mod_cache.c>> mod_disk_cache.c>> mod_mem_cache.c>> mod_log_config.c>> mod_env.c>> mod_setenvif.c>> mod_proxy.c>> proxy_connect.c>> proxy_ftp.c>> proxy_http.c>> mod_ssl.c>> prefork.c>> http_core.c>> mod_mime.c>> mod_status.c>> mod_autoindex.c>> mod_dir.c>> mod_imap.c>> mod_actions.c>> mod_alias.c>> mod_rewrite.c>> mod_so.c>>
And lastly issue...>>
I am reverse proxying to an httpd server instance running on >>127.0.0.1:8081 Have a mem_cache setup that doesnt seem to be >>working....>>
Here are some snippets:>>
CacheEnable mem />>CacheRoot /cache/toppik>>Cach­eSize 5000000>>CacheGcInt­erval 1>>CacheLastModifie­dFactor 0.1>>CacheDefaultEx­pire 3600>>CacheMaxExpir­e 43200>>CacheForceCo­mpletion 60>>#CacheIgnoreCac­heControl On>>CacheIgnoreNoLa­stMod On>>MCacheMaxObject­Count 10000>>MCacheMaxObj­ectSize 12800000>>MCacheMin­ObjectSize 0>>MCacheRemovalAlg­orithm LRU>>MCacheSize 100000>>
There are some disk cache related things in there as I was playing>>around with it during test.>>
and the mod-rewrite stuff that proceeds the cache entries in the config >>file>>
RewriteEngine On>>
# send all requests to www>>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>>RewriteCond %{HTTP_HOST} !^$>>RewriteCond %{SERVER_PORT} ^443$>>RewriteRule ^/(.*) https://www.toppik.­info/$1 [L,R]>>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>>RewriteCond %{HTTP_HOST} !^$>>RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]>># tracking rewrite>>RewriteCon­d %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*) RewriteRule >>^/s-([^/]+)/(.*) /s-$1&kw=%2/$2?%1&%­3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­ # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2>>[R,L]>>­RewriteRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P] RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*) /$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P] # static file rewrite #RewriteRule /(server.*) /$1 [L] RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]>>
Standard response header example:>>
Date: Sun, 21 Nov 2004 04:34:49 GMT>>Server: thttpd/2.25b 29dec2003>>Content-­Type: text/html; charset=iso-8859-1>­>Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT>>Accept-Ranges:­ bytes>>Content-Leng­th: 35484>>Cache-Contro­l: max-age=43200>>Expi­res: Sun, 21 Nov 2004 16:34:49 GMT>>
Some where o where do I have this misconfigured?>>Ord­er that module compiled in?>>Something esoteric in the setup?>>Freaky rewrite rule getting in the way?>>
Your help greatly appreciated...>>
-Sean->>
-----------------­--------------------­--------------------­------------>>The official User-To-User support forum of the Apache HTTP Server >>Project. See <URL:http://httpd.a­pache.org/userslist.­html> for more >>info. To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org>> " from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg>>For additional commands, e-mail: users-help@httpd.ap­ache.org>>
------------------­--------------------­--------------------­----------->The official User-To-User support forum of the Apache HTTP Server Project.>See <URL:http://httpd.a­pache.org/userslist.­html> for more info.>To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org> " from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg>For additional commands, e-mail: users-help@httpd.ap­ache.org>



-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org
Add comment
Axel-Stéphane SMORGRAV 23 November 2004 10:17:44 permanent link ]
 Doesn't it even say something like "cache: no cache" ??

Could you mail the relevant parts of the logs?

-ascs

-----Message d'origine-----
De : Sean T Allen [mailto:sean@usaherbals.com]
Envoyé : lundi 22 novembre 2004 16:53
À : users@httpd.apache.­org
Objet : Re: [users@httpd] RE :mod_cache: how to determine its running


Well what i see for debug output is the content getting cached... then nothing... only access log, no debug information and the response header continues to read thttpd ( yet you'd think it'd see the
proxy debug output
but I don't ).

I am thoroughly stymied by now.

Axel-Stéphane SMORGRAV wrote:
The headers are cached along with the document, and they are served by >the cache.>
As far as headers are concerned, in your case the back-end server is >thttpd; if the document is served from your Apache cache I believe the >Server header should read "Apache".>
If you turn on debug, you'll figure out how to determine whether a file >is cached, and whether it is server from cache, very easily. The debug >output from the cache modules is very explicit.>
-ascs>
-----Message d'origine----->De : Sean T Allen [mailto:sean@usaherbals.com]>Envoyé : lundi 22 novembre 2004 16:07>À : users@httpd.apache.­org>Objet : Re: [users@httpd] RE :mod_cache: how to determine its running>
My question then becomes... what should i see in the logfile that would>indicate that a file is being served from>the cache. And why if a file was cached, would i see headers from the >server it was originally proxied from...>
Axel-Stéphane SMORGRAV wrote:>
To answer the question in the subject line, set the LogLevel to debug>>and look in the error log. That should enable you to determine whether >>a particular document is cached, and if it is not, determine the reason >>for that.>>
From the look of the response headers the document should be cached.>>
You should also have a look at the request headers and make sure that>>>there is no "Cache-Control: no-cache".>>>
-ascs>>
-----Message d'origine----->>De : Sean T Allen [mailto:sean@usaherbals.com]>>Envoyé : dimanche 21 novembre 2004 04:48>>À : apachehelp>>Objet : [users@httpd] mod_cache: how to determine its running>>
Basics:>>
Server version: Apache/2.0.52>>
Compiled in modules:>> core.c>> mod_access.c>> mod_auth.c>> mod_cache.c>> mod_disk_cache.c>> mod_mem_cache.c>> mod_log_config.c>> mod_env.c>> mod_setenvif.c>> mod_proxy.c>> proxy_connect.c>> proxy_ftp.c>> proxy_http.c>> mod_ssl.c>> prefork.c>> http_core.c>> mod_mime.c>> mod_status.c>> mod_autoindex.c>> mod_dir.c>> mod_imap.c>> mod_actions.c>> mod_alias.c>> mod_rewrite.c>> mod_so.c>>
And lastly issue...>>
I am reverse proxying to an httpd server instance running on>>127.0.0.1:8081 Have a mem_cache setup that doesnt seem to be >>working....>>
Here are some snippets:>>
CacheEnable mem />>CacheRoot /cache/toppik>>Cach­eSize 5000000>>CacheGcInt­erval 1>>CacheLastModifie­dFactor 0.1>>CacheDefaultEx­pire 3600>>CacheMaxExpir­e 43200>>CacheForceCo­mpletion 60>>#CacheIgnoreCac­heControl On>>CacheIgnoreNoLa­stMod On>>MCacheMaxObject­Count 10000>>MCacheMaxObj­ectSize 12800000>>MCacheMin­ObjectSize 0>>MCacheRemovalAlg­orithm LRU>>MCacheSize 100000>>
There are some disk cache related things in there as I was playing >>around with it during test.>>
and the mod-rewrite stuff that proceeds the cache entries in the >>config>>file>>
RewriteEngine On>>
# send all requests to www>>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>>RewriteCond %{HTTP_HOST} !^$>>RewriteCond %{SERVER_PORT} ^443$>>RewriteRule ^/(.*) https://www.toppik.­info/$1 [L,R]>>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>>RewriteCond %{HTTP_HOST} !^$>>RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]>># tracking rewrite>>RewriteCon­d %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*) RewriteRule>>^/s-([^/]+­)/(.*) /s-$1&kw=%2/$2?%1&%­3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­ # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2>>[R,L]>>­RewriteRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P] RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*) /$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P] # static file rewrite #RewriteRule /(server.*) /$1 [L] RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]>>
Standard response header example:>>
Date: Sun, 21 Nov 2004 04:34:49 GMT>>Server: thttpd/2.25b 29dec2003>>Content-­Type: text/html; charset=iso-8859-1>­>Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT>>Accept-Ranges:­ bytes>>Content-Leng­th: 35484>>Cache-Contro­l: max-age=43200>>Expi­res: Sun, 21 Nov 2004 16:34:49 GMT>>
Some where o where do I have this misconfigured?>>Ord­er that module compiled in?>>Something esoteric in the setup?>>Freaky rewrite rule getting in the way?>>
Your help greatly appreciated...>>
-Sean-



-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


Add comment
Sean T Allen 1 December 2004 19:12:58 permanent link ]
 question has i'm seeing something that looks closer to correct...

is the mem cache global or per apache instance?

Axel-Stéphane SMORGRAV wrote:
Doesn't it even say something like "cache: no cache" ??>
Could you mail the relevant parts of the logs?>
-ascs>
-----Message d'origine----->De : Sean T Allen [mailto:sean@usaherbals.com] >Envoyé : lundi 22 novembre 2004 16:53>À : users@httpd.apache.­org>Objet : Re: [users@httpd] RE :mod_cache: how to determine its running>
Well what i see for debug output is the content getting cached... then nothing... only access log, no debug information and the response header continues to read thttpd ( yet you'd think it'd see the >proxy debug output>but I don't ).>
I am thoroughly stymied by now.>
Axel-Stéphane SMORGRAV wrote:>
The headers are cached along with the document, and they are served by >>the cache.>>
As far as headers are concerned, in your case the back-end server is >>thttpd; if the document is served from your Apache cache I believe the >>Server header should read "Apache".>>
If you turn on debug, you'll figure out how to determine whether a file >>is cached, and whether it is server from cache, very easily. The debug >>output from the cache modules is very explicit.>>
-ascs>>
-----Message d'origine----->>De : Sean T Allen [mailto:sean@usaherbals.com]>>Envoyé : lundi 22 novembre 2004 16:07>>À : users@httpd.apache.­org>>Objet : Re: [users@httpd] RE :mod_cache: how to determine its running>>
My question then becomes... what should i see in the logfile that would>>indicate that a file is being served from>>the cache. And why if a file was cached, would i see headers from the >>server it was originally proxied from...>>
Axel-Stéphane SMORGRAV wrote:>>
To answer the question in the subject line, set the LogLevel to debug>>>and look in the error log. That should enable you to determine whether >>>a particular document is cached, and if it is not, determine the reason >>>for that.>>>
From the look of the response headers the document should be cached.>>>
You should also have a look at the request headers and make sure that>>>>there is no "Cache-Control: no-cache".>>>>
-ascs>>>
-----Message d'origine----->>>De­ : Sean T Allen [mailto:sean@usaherbals.com]>>>Envoyé : dimanche 21 novembre 2004 04:48>>>À : apachehelp>>>Objet : [users@httpd] mod_cache: how to determine its running>>>
Basics:>>>
Server version: Apache/2.0.52>>>
Compiled in modules:>>>core.c>>­>mod_access.c>>>mod_­auth.c>>>mod_cache.c­>>>mod_disk_cache.c>­>>mod_mem_cache.c>>>­mod_log_config.c>>>m­od_env.c>>>mod_seten­vif.c>>>mod_proxy.c>­>>proxy_connect.c>>>­proxy_ftp.c>>>proxy_­http.c>>>mod_ssl.c>>­>prefork.c>>>http_co­re.c>>>mod_mime.c>>>­mod_status.c>>>mod_a­utoindex.c>>>mod_dir­.c>>>mod_imap.c>>>mo­d_actions.c>>>mod_al­ias.c>>>mod_rewrite.­c>>>mod_so.c>>>
And lastly issue...>>>
I am reverse proxying to an httpd server instance running on>>>127.0.0.1:8081­ Have a mem_cache setup that doesnt seem to be >>>working....>>>
Here are some snippets:>>>
CacheEnable mem />>>CacheRoot /cache/toppik>>>Cac­heSize 5000000>>>CacheGcIn­terval 1>>>CacheLastModifi­edFactor 0.1>>>CacheDefaultE­xpire 3600>>>CacheMaxExpi­re 43200>>>CacheForceC­ompletion 60>>>#CacheIgnoreCa­cheControl On>>>CacheIgnoreNoL­astMod On>>>MCacheMaxObjec­tCount 10000>>>MCacheMaxOb­jectSize 12800000>>>MCacheMi­nObjectSize 0>>>MCacheRemovalAl­gorithm LRU>>>MCacheSize 100000>>>
There are some disk cache related things in there as I was playing >>>around with it during test.>>>
and the mod-rewrite stuff that proceeds the cache entries in the >>>config>>>file>>>­
RewriteEngine On>>>
# send all requests to www>>>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>>>RewriteCond %{HTTP_HOST} !^$>>>RewriteCond %{SERVER_PORT} ^443$>>>RewriteRule­ ^/(.*) https://www.toppik.­info/$1 [L,R]>>>RewriteCond %{HTTP_HOST} !^www\.toppik\.info­ [NC]>>>RewriteCond %{HTTP_HOST} !^$>>>RewriteRule ^/(.*) http://www.toppik.i­nfo/$1 [L,R]>>># tracking rewrite>>>RewriteCo­nd %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?­(.*) RewriteRule>>>^/s-(­[^/]+)/(.*) /s-$1&kw=%2/$2?%1&%­3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*­) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1­&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*) RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2­ # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/m­p)+/(.*)$ http://127.0.0.1:80­80/$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.­*)$ http://127.0.0.1:80­80/$4 [P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$ https://www.toppik.­info/admin/$1 [R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$­ https://www.toppik.­info/$1/admin/$2>>>[R,L]>­>>RewriteRule ^/(s-[^/]*)/admin/(.*)$­ http://127.0.0.1:80­80/$1/admin/$2 [P] RewriteRule ^/admin/(.*)$ http://127.0.0.1:80­80/admin/$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*) /$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule /(awstat.*) http://127.0.0.1:80­80/$1 [P] # static file rewrite #RewriteRule /(server.*) /$1 [L] RewriteRule (.*)$ http://127.0.0.1:80­81$1 [P]>>>
Standard response header example:>>>
Date: Sun, 21 Nov 2004 04:34:49 GMT>>>Server: thttpd/2.25b 29dec2003>>>Content­-Type: text/html; charset=iso-8859-1>­>>Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT>>>Accept-Ranges­: bytes>>>Content-Len­gth: 35484>>>Cache-Contr­ol: max-age=43200>>>Exp­ires: Sun, 21 Nov 2004 16:34:49 GMT>>>
Some where o where do I have this misconfigured?>>>Or­der that module compiled in?>>>Something esoteric in the setup?>>>Freaky rewrite rule getting in the way?>>>
Your help greatly appreciated...>>>
-Sean->>>
------------------­--------------------­--------------------­----------->The official User-To-User support forum of the Apache HTTP Server Project.>See <URL:http://httpd.a­pache.org/userslist.­html> for more info.>To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org> " from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg>For additional commands, e-mail: users-help@httpd.ap­ache.org>



-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org
Add comment
 

Add new comment

As:
Login:  Password:  
 
 
  
 
Ïîæàëóéñòà, îòíîñèòåñü ê ñîáåñåäíèêàì óâàæèòåëüíî, íå èñïîëüçóéòå íåöåíçóðíûå ñëîâà, íå çëîóïîòðåáëÿéòå çàãëàâíûìè áóêâàìè, íå ïóáëèêóéòå ðåêëàìó è îáúÿâëåíèÿ î êóïëå/ïðîäàæå, à òàêæå ìàòåðèàëû íàðóøàþùèå ñåòåâîé ýòèêåò èëè ÓÊ ÐÔ.


QAIX > Apache HTTP Server > mod_cache: how to determine its running 1 December 2004 19:12:58

see also:
[NB 3.2] Relase Candidate 4
Another synchronization issue
[Fwd: projects-dev Digest 2 May 2001…
ïðîéäè òåñòû:
see also:
Aaaaaaaaaaaaaa!!!! Where all…
C prazdnikom vcex!
MOJA PYKA

  Copyright © 2001—2008 QAIX
Idea: Miñhael Monashev
Ïîìîùü è çàäàòü âîïðîñû ìîæíî â ñîîáùåñòâå support.qaix.com.
Ñîîáùåíèÿ îá îøèáêàõ îñòàâëÿåì â ñîîáùåñòâå bugs.qaix.com.
Ïðåäëîæåíèÿ è êîììåíòàðèè ïèøåì â ñîîáùåñòâå suggest.qaix.com.
Èíôîðìàöèÿ äëÿ ðîäèòåëåé.
Write us at:
If you would like to report an abuse of our service, such as a spam message, please .