Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.


#121 add a "blanked" crunch reason


Add a "blanked" crunch reason for pages blocked with +handle-as-empty-document when handle-as-empty-doc-returns-ok is set.

I couldn't log into sourceforge earlier today. Turns out the problem was default.action has
{+block{Site-specific block pattern matches.} }

It used to be trivially easy to debug this type of problem using HttpFox, but 0.8.4 doesn't work with FF 3.6.3 and the current version of HttpFox
a) just gives the result code, not the full result (eg. "200" v. "200 Request blocked by Privoxy")
b) gives a result code of "(Error)" for https requests regardless of Privoxy blocking the URL with a 200 or 403 status

So... add a new crunch reason of "Blanked" to make it easier to debug these kinds of problems.

old log message:
Crunch: Blocked:

new log message after adding
{ +block{ssl sites} +handle-as-empty-document -handle-as-image }
to user.action:
Crunch: Blanked:

Dunno if you want to keep all the
log_error(LOG_LEVEL_HEADER, "Returning status: %s", rsp->status);
log messages in - that was my first cut at figuring out the problem.


  • Lee

  • Fabian Keil
    Fabian Keil

    Now that the Firefox bug is supposedly fixed, I hope we can remove the handle-as-empty-doc-returns-ok option before the next release.

    Also I'd say the crunch reason for blocked requests is always "blocked", no matter how they are blocked. If we were to mention how requests are blocked, I think it should be done independently of the crunch reason.

  • Fabian Keil
    Fabian Keil

    • status: open --> pending
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

    • status: pending --> closed