[Rack] Noisebridge Domain Question

Jonathan Lassoff jof at thejof.com
Thu Dec 6 09:18:30 UTC 2012

I find that once I generally use the fuzzy history search features of most
modern browsers to enter URLs.
A repeat visitor should hopefully have autocompletion or their memory help
them get the one true URL (https://noisebridge.net).

For those that don't know, and may just guess noisebridge.com, or .org -- I
think running a HTTP redirector on there that 301s users to
https://noisebridge.net/ would be useful in those cases.

Andy, or someone with access to the noisebridge.net box, how about:

- Standing up authoritative zone configurations for noisebridge.{net,org}
-- TLD delegations appear the same as .net
- Having whatever backs HTTP (Apache?) send 301 redirects to the HTTPS
service. Maybe mod_rewrite?


On Thu, Dec 6, 2012 at 12:54 AM, James Sundquist
<sundquistjames at gmail.com>wrote:

> On 12/5/2012 11:02 AM, Rubin Abdi wrote:
>> It would be great if (*.)noisebridgenet.org and .com at just port 80
>> would do an http redirect over to noisebridge.net:443, ignoring anything
>> coming into port 443. If I was asked to make a guess I would say that
>> the majority of hits to those two TLDs would be for port 80 and not 443.
>> If someone's hitting 443 they're simply sorely misinformed and are most
>> likely educated enough to try knocking on 80 next.
>>  For me, access through https is far less important than the website
> simply connecting to somewhere other than an error message.  Getting Port
> 80 working sounds like a reasonable place to start.
> ______________________________**_________________
> Rack mailing list
> Rack at lists.noisebridge.net
> https://www.noisebridge.net/**mailman/listinfo/rack<https://www.noisebridge.net/mailman/listinfo/rack>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.noisebridge.net/pipermail/rack/attachments/20121206/97c6f7a9/attachment.html>

More information about the Rack mailing list