Access Denied logs generated.
ceinma - August 29, 2009 - 00:21
| Project: | Google Translate Links |
| Version: | 6.x-1.4 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
Hi,
First, sorry for my poor english.
After active the gtranslate_links-6.x-1.4 a lot of "access denied" started to appear on my dblog for each page what I access with my authenticated user. But all works fine without any error message.
A curious is this "access denied" appear with user Anonymous, and not with my authenticated user.
For anonymous users what access my site, all works fine and no log are generated.
I already rebuild access permission, and have no effect
This is a copy of my last dblog (interface is in Portuguese).
aviso access denied 28/08/2009 - 21:02 admin/build/block Anônimo
aviso access denied 28/08/2009 - 21:02 admin/build Anônimo
aviso access denied 28/08/2009 - 21:01 admin/build/modules Anônimo
aviso access denied 28/08/2009 - 20:57 admin/build/modules Anônimo
aviso access denied 28/08/2009 - 20:56 admin/reports/dblog Anônimo
aviso access denied 28/08/2009 - 20:56 admin/settings/performance Anônimo
aviso access denied 28/08/2009 - 20:56 admin/settings/performance Anônimo
aviso access denied 28/08/2009 - 20:54 admin/reports/dblog AnônimoThis is the content of one this logs:
Detalhes
Tipo access denied
Data sexta-feira, 28 Agosto, 2009 - 21:02
Usuário Anônimo
Localização http://******.com.br/informix/admin/build/block
Referência
Mensagem admin/build/block
Severidade aviso
Nome do servidor ***.101.17.230
Operações If I deactivate the gtranslate_links module, this logs stops appear.

#1
Your report is clear, complete and thorough, and that often is more valuable than perfect English ;-)
In short: It's a feature, not a bug.
Long story: Google Translate accesses your site as an anonymous visitor. Therefore, it can't access some of your pages. It would be of no use to display the flag block on those pages; it might even cause confusion and/or disappointment. Sadly, Drupal doesn't seem to have a mechanism in place to answer the question 'is this page accessible for the anonymous user?'. It has one for *nodes*, but not for arbitrary URLs.
To answer this question, then, the module does a HTTP HEAD request on the 'current' URL as the anonymous user. There is a performance impact, but it's quite low, especially if PHP is compiled with libcurl support and caching is enabled.