Says my URL https://www.qkast.com is invalid.
That's odd. UrlRoulette does some sanity checking on the content of the URL. Thank you for this bug report!
Fails for Amazon URLs, too (And no, I didn't include a referral link in there.)
Show HN: UrlRoulette – Pass a URL to the next visitor
41–50 of 143 posts
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#42Adding in a query param to bust the cache make it possible to submit the same site multiple times, i.e. example.com, example.com?1, example.com?a, example.com?123
On the other hand the Link I submitted wouldn't have shown the desired result without the query string.
You probably want to allow repeats of domains, Like map links to something interesting.
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#43Adding in a query param to bust the cache make it possible to submit the same site multiple times, i.e. example.com, example.com?1, example.com?a, example.com?123
Yes, it does, but I think there is almost no way around that. Many sites still use query parameters to show a specific blog entry for example... :/
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#44Just did this, and got redirected to this post. Clever.
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#45I made something similar for Youtube videos: http://youtubeswap.com . Lots of trolls, but it can be fun.
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#46I got meatspinned!
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#47Earlier quoted context omitted.
That's odd. UrlRoulette does some sanity checking on the content of the URL. Thank you for this bug report!
Fails for Amazon URLs, too (And no, I didn't include a referral link in there.)
Amazon rejects obvious non real browser user agents. This app tries to verify urls before putting them in the queue. I think they may have more anti scraper measures as well.
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#48Earlier quoted context omitted.
A server should respond with the same headers to a HEAD request as to a GET one.
SHOULD and DOES are not the same thing. Returning 405 'Method Not Allowed' on a HEAD isn't unreasonable, and that is the issue we are seeing. EDIT: did say GET on prior edit.
> Returning 405 'Method Not Allowed' on a GET isn't unreasonable
I think you meant "on a HEAD".
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#49Adding in a query param to bust the cache make it possible to submit the same site multiple times, i.e. example.com, example.com?1, example.com?a, example.com?123
Yes, it does, but I think there is almost no way around that. Many sites still use query parameters to show a specific blog entry for example... :/
Their server could trivially query the url and store the result hash. This would also give a chance to scan for malicious content
Re: Show HN: UrlRoulette – Pass a URL to the next visitor
#50Earlier quoted context omitted.
A server should respond with the same headers to a HEAD request as to a GET one.
They should, but many good sites just don't, for whatever reason. Even ones you know are run by smart people: $ curl -I -X HEAD https://redis.io/ HTTP/1.1 404 Not Found For this app, being more forgiving is a better idea.
[deleted]