search

censorship-no-archive / ceno1

(Deprecated PoC) Innovative censorship evading technology based on p2p distributed caching network
https://censorship.no
GNU Affero General Public License v3.0
58 stars 14 forks source link

CENO Portal's Visit a URL textbox is not redirecting to the proper link #171

Closed misaakidis closed 8 years ago

misaakidis commented 8 years ago

As a user, I want to use CENO Portal's Visit a Website textbox to look for bundles.

Searching for www.google.com in the textbox opens a new tab to "http://localhost:3090/www.google.com"

arcrose commented 8 years ago

Sounds like you're blocking JS again.

graphiclunarkid commented 8 years ago

We can't reproduce this. @misaakidis, please can you update this bug with reproduction steps, the expected result and the actual result you see. Alternatively, please close this if you can't reproduce it in a vanilla browser.

misaakidis commented 8 years ago

I was using CENOBox's browser before, but can not replicate anymore.

misaakidis commented 8 years ago

Actually I can still replicate, once the page refreshes I get the following error message:

You asked for http://localhost:3090/www.google.com Here's the error we got: Requested URL is invalid

graphiclunarkid commented 8 years ago

OK. Could you write down the exact steps you took to reproduce the bug? @redwire, if this is something you can look at before you leave, please can you commit it to the current sprint?

misaakidis commented 8 years ago

Get CENOBox ./CENO.sh

In the new chrome window go to the respective text box and visit www.google.com You get directed to a normal page "Your bundle is being prepared". First refresh of the page though shows the "Requested URL is invalid" error.

Let me know if you would like me to provide you with the latest CENOBox.

graphiclunarkid commented 8 years ago

The CENOBox build is not current. This needs testing on a client built from the tip of the "next" branch to confirm whether it's still a bug.

misaakidis commented 8 years ago

Using the tip of the "next" branch, I am able to replicate the issue. The problem is somewhere on the redirection from an auto-refresh error page to a bundle lookup page. If you would like to reproduce the issue please follow the steps in my previous comment.