obviated need for invalid_hostname.tpl

[virgil]

I realized that everytime I was showing the invalid_hostname template all I wanted was the user to go back to the front page. So I skipped a step and we have one less template to think about.

[landscape-bot]

Repository health decreased by 33% when pulling f13d91e on virgil:patch-5 into 09dc22e on globaleaks:master.

• 6 new problems were found (including 5 errors and 0 code smells).
• 38 problems were fixed (including 0 errors and 18 code smells).

[landscape-bot]

Code quality remained the same when pulling 08c1358 on virgil:patch-5 into 09dc22e on globaleaks:master.

[evilaliv3]

mmm got the point in the case of onion.city, but what about tor2web.org in general? @fpietrosanti ?

in addition in the case of tor2web.org in general (where we still block crawlers) there is a big issue; if we make the crawlers subject to the banner, the crawler will think the page exists even if the HS does not exists anymore, due to the fact that the acceptance page is shown before making any kind of request to the hidden service. @fpietrosanti what do you think about this issue? crawlers would penalize tor2web for pointing a lot, even not existing pages to the same acceptance page.

[virgil]

This isn't outputting the content of the frontpage, it is redirecting to the frontpage. The former is spammy behavior, the latter is not. Just do a 301 redirect.

[evilaliv3]

yep virgil i see what you sai in relation to onion.city.

the issue would be with tor2web software in generale that does not have an homepage but we could design it to point simply to www+ config.basehost or something.

and for the issue i was saying, @fpietrosanti probably befor showing the disclaimer we should anyway make a requeste to the hidden service requiring simply the "/" in order to test if the page exists or not (this would also speed up things by opening the circuit; so we exploit the time the user opens the page to automatically opening the sock.

[virgil]

Yeah @evilaliv3 makes sense.