Live data from Hacker News

A URL Lengthener

aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.com

11–20 of 313 posts

Re: A URL Lengthener

#13
> Disclaimer: Since there is a maximum letter count to a URL, there is a slight chance your resulting URL will be too long to use. No worries, try running it through a site like bit.ly and then paste that one over here. Every resulting URL ends up having a minimum number of characters, so your URL will still be plenty long!

This seems like something you can trivially solve yourself. Is there any good reason why you push this issue on the user?

Re: A URL Lengthener

#14
post #7

Earlier quoted context omitted.

It could be shorter still! Stop forcing HTTPS!

HTTPS is not required. t.ly works fine without " https:// "

Really? The browsers I usually use to test if a site works without HTTPS (IE6 and IE8 on XP SP2) can't load it. Weird!

Re: A URL Lengthener

#15

> Disclaimer: Since there is a maximum letter count to a URL, there is a slight chance your resulting URL will be too long to use. No worries, try running it through a site like bit.ly and then paste that one over here. Every resulting URL ends up having a minimum number of characters, so your URL will still be plenty long! This seems like something you can trivially solve yourself. Is there any good reason why you p…

It's possible that this project is intended as humor, and a humorous workaround achieves that better than a technical fix.

Re: A URL Lengthener

#16

> Disclaimer: Since there is a maximum letter count to a URL, there is a slight chance your resulting URL will be too long to use. No worries, try running it through a site like bit.ly and then paste that one over here. Every resulting URL ends up having a minimum number of characters, so your URL will still be plenty long! This seems like something you can trivially solve yourself. Is there any good reason why you p…

There isn't really "a" maximum count. There's a variety of enforced limits. If the standard(s) even set an official one, it's not something a lot of things pay attention to. You also can encounter problems with things like command lines enforcing their own limits, making a URL that your browser may or may not be happy with not be something you can directly curl or wget.

Re: A URL Lengthener

#17
fun fact. in the browser wars of 1993(?) i looked at the specs from netscape (mozilla dady for the young folks) and microsoft (what w3c? ha!) and netscape release a browser spec that said "X must support up to Y", as in "url must be up to 1024 chars", "cookies must be up to 1mb", etc...

then microsoft release IE4 (or 6?) web spec. It was literally a copy of netscape's but with "up to" replaced with "at least".

and from this day on, nobody knows about limits on the standard and everything was up in the air, just so sites could work on IE4 and be broken on netscape. Thanks microsoft!

I did some experiments to test the actual URL limit of IE. at the time it was around 4MB, but IE would still go over if you got creative with hostnames levels and odd schemas.

-- quick edit:

keep in mind, in 1993, the money from giving out free browsers where on the servers: netscape server vs microsoft IIS (just like today giving free browsers the money is on makig it easier to access YOUR content --e.g. default search, etc).

Making your browser crash the competitor server mean that server was seen as lower quality. (Same thing with google deliberately crashing performance of firefox on their services today[0])

The point of microsoft making this change was to force netscape to update their server as they increase the URL limit arbitrarily to all IE users.

[0] https://www.zdnet.com/article/former-mozilla-exec-google-has...

Re: A URL Lengthener

#18

haha nice! I built the exact opposite the shortest possible URL shortener :) https://t.ly/

For many years (but no longer) Vince Cate's Offshore Information Services had a DNS A record for the ccTLD "ai", so that http://ai/ was a valid URL that worked in browsers. (A few people also had e-mail addresses @ai.)

Today, there are no longer any TLDs of any kind with their own A records.

https://www.internic.net/domain/root.zone

Re: A URL Lengthener

#19
post #14

Earlier quoted context omitted.

HTTPS is not required. t.ly works fine without " https:// "

Really? The browsers I usually use to test if a site works without HTTPS (IE6 and IE8 on XP SP2) can't load it. Weird!

the http url is a 301 redirect to https so thats why it doesn't load ultimately
Post reply on HN