So this is one thing that drives me crazy, no SSL support!

Anyway, I know we can only run one "forum", what if I copy the directory and change my URL to https://forums.wolfram-studios.com

Does that still count as one forum right? THEN I'd have SSL support (though I'd have to copy all updates to it, not a problem)

Your allowed one public installation of the forum. How you go about this, is entirely up to you, just as long as its 1 public installation.

Your allowed a private installation of course, just nobody can register or login, its meant just for tests.

Well I mean I guess it's one installation, it's one database, just split between an SSL copy and a non-SSL copy. Basically I have a copy at
http://forums.wolfram-studios.com
https://ssl.wolfram-studios.com/forums

They are actually different physical copies, the only difference between them is the base URL (yes this causes problems in uploaded files and avatars... grr it's a quick fix to a long term problem) the copies are on the same machine, but in different folders.


Thing is even modifying the base URL to have https in it didn't work fully, avatars don't work, and blogs don't work.

It's not a biggie, SSL was just to be used for some filter avoidance back in my highschool days, but we still have highschool users, so I leave the option open.

So SSL support on the same installation is kind of a huge feature that I'd like.

Um, IPB works fine under SSL.

One installation of IPB does *not* work off of two physical locations, because you can only specify ONE url. And even then, if you could specify two, it's beyond IPB's capabilities to be copying files from one install to another at this point.

Yeah I've been testing it out, while it lets me read threads and post, I must have an image URL to work. I find it strange to force all users under SSL, so I just use it as a imageless version for SSL. Plus SSL puts more strain on the server (bad news for my old server).

I mean if I put them both at forums.wolfram-studios.com, IPB can't tell the difference between http and https by itself, it's part of the physical code. Thats where my problem lies in.

If you install under SSL, and your board url is https://forums.domain.com, and that is what is written to conf_global....it works fine.

If you install under http, it works fine.

But, you cannot have it both work under SSL and http at the same time - IPB is only designed to hold one url, so when it generates links, it uses the url in conf_global, not what was requested.

Thats why I say it should be a feature, being as it's useful to have both.

This seems like a feature that isn't needed.

If you don't have the hardware to use SSL then you shouldn't use it or upgrade your hardware. I don't see alot of people needing this, anyone who does use SSL has paid a good amount of money for it and wants to use it and only it most of the time.

I use SSL at my site and forums on IPB Tutorials and as Brandon said, just make the conf_global file with the proper variables/settings to format it correctly for SSL Support (https://). I don't think there is a need for this feature, to be honest.

SSL is software (actually just a certificate at that) and I have it fine, and SSL only runs less than 10 dollars a month (though I run a free one, the company said it's okay to run an out of date certificate, you just get messages), plus running constant SSL takes more CPU power, which I don't have for all the users and bots that scan my site.



I set that up, and it works okay, except for images, because of the blogs you need to set an image server, the image server of course is going to be non-ssl, being as thats the most used site.

Right now using your idea, most of it works, you can login and post, but you get no images or blog access.

I dunno I mean I guess it works good enough