New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data URLs, such as those created by image inlining, clutter the log with spurious warning messages for downstream filters #36

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

For example:

[Sun Nov 07 00:33:25 2010] [warn] data:image/
png;base64,iVBORw0KGgoAAAANSUhEUgAAACcAAAAoCAYAAAB99ePgAAAQmElEQVQY07XPCTTV...CC
: Invalid url relative to
'http://www.arhiram.ro/index.php?q=stiri/2010/03/astazi-va-avea-loc-
procesiunea-de-florii-arhiepiscopia-ramnicului&page=82'

We should be detecting when the scheme is 'data' and skip the Domain validation 
check (and warning).

Original issue reported on code.google.com by jmara...@google.com on 7 Nov 2010 at 1:37

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

looking forward for a fix on this because... on a many vhosts(100+) server the 
logs are ... flooded with this kind on entries and server dies after 20-30 
minutes (depending on  the traffic)

Original comment by raduta.a...@gmail.com on 7 Nov 2010 at 11:10

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

I'll try to work up a fix this evening.  This ought to be reasonably easy to 
fix.

Original comment by jmaes...@google.com on 7 Nov 2010 at 6:59

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

This ought to be fixed by the recent logging changes; you'll still see the 
noise if you crank the log level up high.

Original comment by jmaes...@google.com on 9 Nov 2010 at 2:38

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment