What is the reason for that change?harvey wrote: The Web server now declares all its Web pages to be in iso-8859-1
(character encoding), which was changed from utf-8 in the past few days.
Code: Select all
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">DigiSage wrote:Why did this happen?
It's a long story. Here it is.
There are a lot of other sites on this same server. The server has 8gbit/s of bandwidth and plenty of CPU/RAM to go around, so this shared hosting environment usually works just fine. I've had several sites "slashdotted", as well as linked to by cnn.com, news.com, other big sites, never had any problems.
Recently, one site sent out a mass email ... This caused an extremely high increase in traffic to their web site. Much, much more than anything I've ever gotten from slashdot or anything else.
Anyway, this traffic totally overloaded the server. It prevented basically every site from working... I had to do something to fix the issue. As a temporary fix, I shut down that site, which helped a bit, but didn't totally "fix" the issue because there was still a ton of traffic, people were just being served a "this site is disabled" message instead of their actual site.
While the server was a little less broken, thanks to taking their site down, I looked into what my options were. We were running apache v1.3 at the time. I knew that Apache2.0 was much, much more efficient. We hadn't upgraded to Apache2.0 before because we didn't need the better performance, and the potential for causing problems with php sites (among other things) was high.
Well, at this point in time, I didn't really have a choice. So I upgraded to Apache2, which required upgrading php, all of php's modules, and I also upgraded MySQL while this was going on, also for performance increase reasons.
Once I brought the new Apache2 up, the whole server went back to normal, as far as performance goes. In fact I'd say that it's faster than it was before. But anyway, somewhere along all these upgrades, the character encoding issues appeared. It's an extremely common problem, especially when moving from apache1 to apache2.
So, this server software upgrade is what broke the Librivox forums, and for that you have my most sincere apologies. Unfortunately this sort of thing happens on shared hosting servers. As much as web hosts try to avoid it, things like this happen. The only sure-fire way of avoiding it is to get your own dedicated server, which costs a lot of money.
I've made changes to the forum software, Apache2.0, php and MySQL to ensure that ALL new data entered into MySQL from this forum or anywhere else will guaranteed be stored as UTF-8. And I've forced the forum software to always display in UTF-8. So this problem shouldn't happen again.
Eh?Xander wrote:WOW!! I didn't know that a simple little problem I had could expand into something so massive and technical. I thought it was just some configuration error on my part.
Fixed! :)kristin wrote:I was just looking at the first post of Pirates and noticed some of the ' and " and - are now ?.a.r.dobbs wrote: If you see something that still needs help, please note it here. Thanks!
