Yeah, looks fixed now. ;)

Some of the file corruption fun induced by NFS disappearing out from under a VM. It was fixed earlier, thanks.

Just wanted to agree with the previous post-  easy, fast, powerful… nuff said

Yeah, it seems to work now. Thanks.

They're redirects from the old page name to the new, they all work that I've seen. It was broken before that in places that linked to http://doc… rather than HTTPS, the Apache redirect turned the %3F into ? in the HTTPS URL and broke the links until that was done. If you know of any links that aren't working, please give examples.

@jimp:

I haven't seen any for me.

Something like that :

Delivered-To: <<me>>
Received: by 10.50.97.99 with SMTP id dz3csp19462igb;
        Thu, 19 Dec 2013 09:38:55 -0800 (PST)
X-Received: by 10.224.124.16 with SMTP id s16mr5176503qar.78.1387474735562;
        Thu, 19 Dec 2013 09:38:55 -0800 (PST)
Return-Path: forum@pfsense.orgReceived: from mail.pfsense.org (mail.pfsense.org. [2610:160:11:4::10])
        by mx.google.com with ESMTP id r5si3441110qat.160.2013.12.19.09.38.55
        for <<<me>>>;
        Thu, 19 Dec 2013 09:38:55 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of forum@pfsense.org designates 2610:160:11:4::10 as permitted sender) client-ip=2610:160:11:4::10;
Authentication-Results: mx.google.com;
      spf=pass (google.com: best guess record for domain of forum@pfsense.org designates 2610:160:11:4::10 as permitted sender) smtp.mail=forum@pfsense.org
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.pfsense.org (Postfix) with ESMTP id E8AC520232
for <<<me>>>; Thu, 19 Dec 2013 12:38:54 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.pfsense.org
Received: from mail.pfsense.org ([127.0.0.1])
by localhost (mail.pfsense.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id sCnct5zOPd1H for <<<me>>>;
Thu, 19 Dec 2013 12:38:54 -0500 (EST)
Received: from mail.pfsense.org (unknown [172.27.3.13])
by mail.pfsense.org (Postfix) with SMTP id 264A620225
for <<<me>>>; Thu, 19 Dec 2013 12:38:54 -0500 (EST)
Subject: New Password Details
To: <<<me>>>
From: "pfSense Forum" forum@pfsense.orgDate: Thu, 19 Dec 2013 17:37:17 -0000
X-Mailer: SMF
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="SMF-9cb688b3ea00b0a32cd17164a39bedbb"
Content-Transfer-Encoding: 7bit
Message-Id: 20131219173854.264A620225@mail.pfsense.org

Hey, <<me>>!

Your login details at pfSense Forum have been changed and your password reset. Below are your new login details.

Your username is "<<me>>" and your password is "exxxxxxxx1".

You may change it after you login by going to the profile page, or by visiting this page after you login:
http://forum.pfsense.org/index.php?action=profile

Regards,
The pfSense Forum Team.
–SMF-9cb688b3ea00b0a32cd17164a39bedbb
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hey, <<me>>!

Your login details at pfSense Forum have been changed and your password reset. Below are your new login details.

Your username is "<<me>>" and your password is "exxxx1".

You may change it after you login by going to the profile page, or by visiting this page after you login:
http://forum.pfsense.org/index.php?action=profile

Regards,
The pfSense Forum Team.
--SMF-9cb688b3ea00b0a32cd17164a39bedbb--</me></me></me></me>/forum@pfsense.org</me></me></me></me></me>/forum@pfsense.org</me>

strange :-/

Edit : OK !
lsf has done some changes on my account (PM at 6:32 PM GMT+1), 3 emails at 6:30 PM GMT+1 and 6:37, and another one at 6:37

@cmb:

[…] your session will be invalidated after an hour of inactivity.

thats the problem… independent of (in-)activity the session expires after 60 minutes per default.
Thats a "nice" feature if your post go into /dev/null when posting (even with several previews before...

AGREE!!

"IE10 is actually a very good browser!"

Yes - I was particularly impressed with IE10 the other day when visiting a site with a self signed cert and the only option provided was not to go to the site.  It was quite a fulfilling experience.  Luck for me both Chrome and Firefox had no problems.

I dont Jim and thats why I asked before clicking any links in it and reporting it as spam :D

You can do this now (and have been able to for years) with port aliases. Firewall > Aliases, make a new alias of the type "ports" and put in 80, 22, 21, 443. Then set the port on the NAT rule to 'other' and enter the alias name.