Apache 2.0.48 Released
Gruturo writes "Busy week for the Apache software foundation:
After 1.3.29, version 2 gets an update as well with 2.0.48, which mainly fixes these two security vulnerabilities.
As usual, using a mirror is recommended." The official announcement lists several changes as well.
better luck next time
were covered earlier on slashdot here
'nuff said
GENERATION O98346: The first time you see this, copy it into your sig and remove a random number from the generation. T
And my server is safe, secure and can take a slashdotting.
This has nothing to do with anything remotely Slashdot related, but I need to do something before my head explodes...
As I type this, my roomate and my best friend/recent lover are fucking in the next room over. WHAT THE FUCK. After 10 years of friendship and built-up sexual tension, we finally hooked up and now less than a week later she's banging my roomate. I am so fucking incensed right now I can't think straight. I wouldn't mind if they went to a hotel or otherwise didn't make it known, but she just FUCKING WALKED PAST MY ROOM TOPLESS AND SHUT THE DOOR IN MY FUCKING FACE. How fucking insensitive can you be?!
This sucks. It's 3AM and I'm telling strangers (GEEK strangers, no less) about my personal problems. I am a big pussy and will most likely not say anything to either one of them so I expect this to go on for a while. Fuck.
Feeling low? There's someone else out there that's having a worse day than you. Trust me.
This shows that there are some 3l337 haxors on the reservations.
http://www.cgisecurity.com/webservers/apache/
so there i wass bllllasss deep ing this chick:
oh yeah:
60% grape soda,
20% orange juice,
20% vodka,
ice.
"Dimatap"
Here's how Flash puts it, having been scalped: "You see, it's been the great illusion of our civilization that when the poor heathen saw our steamships and elections and drains and bottled beer, he'd realize what a benighted ass he'd been and come into the fold. But he don't. Oh, he'll take what he fancies, and can use (cheap booze and rifles, for example) but not on that account will he think we're better. He knows different . . . And it doesn't help when the two sides regard each other respectively as greedy, brutal white thieves and beastly, treacherous red vermin. I'm not saying either was wrong."
GENERATION O98346: The first time you see this, copy it into your sig and remove a random number from the generation. T
Biatch!
We've been running the beta of this release on our staging web server cluster. We find that this solution integrates nicely with our Sonic Foundry LocalDirector content server. I think the Apache team outdid themselves by providing a nice API that integrates nicely with most the commercial application servers such as Tomcat, Iris, and ISA Server.
.NET framework for Solaris we would definately be able to unleash some more serious functionality.
Where it really shines is in the mySQL performance when residing on the server. I'm very keen to have our team roll out the new version asap on our production environment since we find that the DBAs find the performance lacking compared to Oracle's WebSphere. If Ximian would only release the
Which is nice.
you feel better
Generally RedHat will not put in new packages at the last minute. But this is a security fix release only and also Fedora is considered more experimental than regular Redhat releases.
Maybe Debian Stable can finally update their Apache packages??? I'm still running 1.3.26... jeez!
I for one welcome our new Apache overchiefs.
United States of America, good ol' backers of world peace.
I saw this post a couple of weeks back.
Be original, create your own trolls.
It will take all November to compile it :(
If you click the link above you may be charged under the DMCA. That information is only for people with the right authorization. You most likely do not have it.
An Apache point release on the front page? Can you say "slow news day"?
It's hard to be religious when certain people are never incinerated by bolts of lightning.
2.0.48 is released!
This is the defining moment of my life. I have been continually pressing the "refresh" button since the story about 2.0.47 being released. Now all my hard work has paid off.
2.0.48 is released at last!
I am leader of the free world... and I can even write poetry! Look what I wrote for my wife a few weeks ago...
Roses are red
Violets are blue
Oh my, lump in the bed
How I've missed you.
Roses are redder
Bluer am I
Seeing you kissed by that charming French guy.
The dogs and the cat, they missed you too
Barney's still mad you dropped him, he ate your shoe
The distance, my dear, has been such a barrier
Next time you want an adventure, just land on a carrier
I have all the power.. like that He-Man guy on the cartoon channel. All my buddies can buy and sell you... the big underground star chamber of corp. bigwigs are gonna buy me an island to live on after I destroy this country and feed it to the corps. Fuck all of you... who needs you? The corporations OWN YOU!
"W"
Yay, Apache! More proof open source software works.
"If you are a dreamer, a wisher, a liar, A hope-er, a pray-er, a magic bean buyer
... so I can see, the Knicks play basketball.
...to pay your $1499 licensing fee you cock-smoking teabaggers.
I used Apache 2.0.47 for all of a day before I decided to never use the 2.0.x line again. Apparently when a partial transfer is requested, Apache 2.0.47 logs the full amount requested. Not what was actually transfered. I ended up showing over 10GB of transfer in a single day on a 256Kbit DSL line. Which if you do the math is only physically capable of about 2.5GB a day.
I looked at my logs and determined that a couple AOL users were trying to get a rather large file
aca9bd40.ipt.aol.com 655 6689 1004 310
acc4e74f.ipt.aol.com 1014 5412 521 148
ac8bd972.ipt.aol.com 140 1565 534 745
Requests MB KB Bytes. All that transfer supposedly happened in about a day.
I notified bug-track but apparently such a simple problem (which doesn't exist in the 1.3.x line) isn't worth addressing.
After all, who actually uses the Apache 2.0.x logs to monitor transfer? Hopefully not any hosting companies because the customers are going to get royally screwed.
Ben
Work Safe Porn
Twice. Software that works means it is right, THE FIRST TIME. If this had been MS, you know damn well you'd be all over them for 'buggy' stuff.
All this proves is OSS zealots are hypocrites, with double standards.
Just thought i'd say - the link is a logout link
It seems we are getting these daily now. So much for the cathedral. Seems par for the course regarding FOSS. This is what happens when HOBBYISTS try to copy professionally written software, like something from the Microsoft house. Then again, you get what you paid for.
President George W. Bush
Comment Line: (202) 456-1414
E-mail: president@whitehouse.gov
Secretary of Defense Donald Rumsfeld
Tel.: (703) 692-7100
E-mail: http://www.defenselink.mil/faq/comment.html
10 bucks says my university still doesn't upgrade it's servers from 2.0.40
and my shaving looks good everyday
Do you want good luck to follow you and your offspring for geneations to come? This troll has the solution for you...
All you have to do is copy this troll onto two to four of the discussion threads of your choice! That's right! Just copy this into a new message and click "post anonymously." That's all there is to it! *
Tired of that idiot talking about geek culture! Stick one of these babies on it! And it's good for the economy!
Marge Gentry of Cambridge, Minnesota participated, and the next day she received a large fruit basket outside of her door from a secret admirer. Unfortunately, Marge was hit by a truck the next day, so she didn't get to the Granny Smith apples.
Commander Taco of Hole-in-the-ground West Virginia didn't participate, and he was violated by a group of raging homosexuals. Since the gang was headed by Jon Katz, Taco had no recourse to the law because the entire town knew about their previous relationship. The unfortunate outcome is enshrined forever at goatse.cx.
So if you want to get the fruit basket and not get poked in the bread basket, just copy this troll onto two of the discussions threads of your choice. We could have this place blanketed by sundown!
You don't pay for the oxygen you're breathing, do you?
Do you know if they released 2.0.48 yet?
the new netcraft stats are posted.
apache just keeps stealing more market share-
It's too bad Fedora will not be coming out on Monday.
Yah, as if anyone's going to let you take a lighter to their cock...sheesh...
nice effort
unfortunatly you are dealing with greasy spotty fatso's here who don't know about sex (except with themselves) but they do know about IT products, maybe you would be better off at Yahoo or MSN forums, they like someone experienced
I disagree. That greasy fatsos know nothing.
I am going to punch you in your fat fucking man tits you monkey butter eater
proof
Thank you. I've used up my mod-points.
I just made simple statement that indicated that the original post reflects the sad state of affairs of /. and its moderation system. If you look at my low UID you'll see I've been around here for years so I think I have to right to speak my mind.
For the pollyannish ...
e dule/
From:
http://fedora.redhat.com/participate/sch
Schedule
Fedora Core 1 / Cambridge
* July 21 2003 - Test 1 (originally called Beta 1) release
* September 25 2003 - Test 2 release
* October 13 2003 - Test 3 release
* November 3 2003 - General Availability
I bet you'd just looooooove a good teabagging, you cock-smoker. Just like your daddy used to.
Should I upgrade?
Or should I hold out for 2.0.49?
sorry to burst your bubble, but...
Are people using 2.0 much yet? I remember all of the blowup over how 2.0 didn't really add anything unless you wanted to run it on Windows, and it caused a lot of problems for modules like mod_perl. Is everyone still sticking with 1.3?
See this.
This version was released the same day as 1.3.29 earlier in the week, Wednesday, I believe. Perhaps future posters would consider combining this news into one post.
When trying to get your software announced on freshmeat.net, has anyone else got pissed off with how long it takes the editors to post your announcement on the front page.
When it does finally appear, it appears in the same batch as hundereds of other announcements and goes off the front page straight away. Grr...
Why are there two branches of Apache? There's the 1.3 and 2.0 lines. I've heard that 1.3 is better than 2.0, so is 2.0 effectivelly a beta? Why are there still new releases of 1.3, why not concentrate on 2.0?
> We had to respin FC1 today for a non-technical issue
What the heck is "respin" ?
Apache 2.0.48 works extremely well on windows 2000 there are no problems such as hanging during shutdown for me anymore one qualm i have is that the configuration could be made a bit easier using a web based interface like the one which abyss web server from www.aprelium.com has i look forward to a long and happy life with apache MC
The "Monitor Apache Servers" program seems to have a weird effect on the windows API when it is visible for example copy and paste wont work very well if at all, minimizing the window fixes the problem very weird all in all a better apache
Very true. I clicked on it and thirteen seconds later my phone rang. Very scary. If they called me that fast I wonder how long it'll take them to knock on my door and drag me out of mHGJEG(&R^TG(&^R(&IORGO*&RGOUYGYGROUYGIUYKGIKFBGYK FBGFGKGBKUYGOYUGOUYG
That fix should be standard. Obviously Apache knows about the problem but even when someone fixes it for them (so writting a fix myself as someone else suggested is a worthless pursuit to try to actually fix the problem) they continue to insist on ignoring the problem and linking by default to a known broken module that they refuse to fix. And on top of that, they fail to properly document the workaround.
Most web-site owners are more interested in running their business than dicking around with source code. Even if they knew how to even begin looking for the problem spot. I opted to revert back to 1.3.x since it's solid.
This reflects very poorly on Apache in regards to their attitude about bugs. Especially considering this shouldn't have been broken from the first 2.0 release.
"We know about it, but we don't care to fix our default logging module" is pretty sad.
It's nice to know a workaround exists but when something as simple as logging can't get an official fix it does very little to instill confidence in the product.
Maybe I'll give 2.0 another try later with my personal server but the server my business runs on will be sticking with 1.3. It works great and so I can just focus on running the business and writting source code for a job instead of reinventing fixes for a wheel that's been known to be broken for a very long time.
Ben
Work Safe Porn
Doesn't go over well with business people. I do programming as a profession. However, when the 1.3.x line is flawless it's hard to convince myself it's worth my time to tackle this problem. Considering how many people have downloaded and rely on the 2.0 line, I wonder how many have the skill or motivation to fix such a glaring and simplistic flaw that should never have existed.
Especially considering someone did take the time to write a logging module that works and Apache still refuses to make it the standard, insisting instead to link to the default, "approved," known to be broken one.
By telling me to "fix it myself" he was basically telling everyone to ignore the fact that Apache is ignoring already existing fixes and needlessly reinvent the wheel themselves.
I'd actually be happier not knowing the fix existed. Apache's actions would make more sense (and be more acceptible) because I could pretend it was a complicated issue still in progress.
Ben
Work Safe Porn
I do programming as a profession
Oooh. Am I supposed to bow to your mightiness? Frankly, you've already swept me off my feet.
By telling me to "fix it myself" he was basically telling everyone to ignore the fact that Apache is ignoring already existing fixes and needlessly reinvent the wheel themselves.
No, actually, he was basically telling you to fix it yourself, no need to read into it. If you're such a programming professional, it should be trivial to fix. Apache isn't someone you pay for something to work. It, like all other OSS projects, only get better when people get off their butt and fix problems. However, I'd rather have it stay broken and get fixed by someone decent than for it to grudgingly get fixed by as it's obvious you are a leech on open source's inner thigh.
I MUST KNOW!
If the Apache team wants everyone to adopt 2.x, they better make sure it works flawlessly. Or at least as good as the 1.x line. I agree with Ben, and I'm not the only one (a lot of admins still like 1.x better) and I'm not upgrading until all the shit works right. Production sites should only run the most stable and bug-free code, and that means 1.x for now and maybe quite some time into the future if what Ben described was true (the part about the Apache developers not caring enough to use a working subsystem instead of the standard, but broken version).
Saving lots of memory: Just run in 'worker' mode, and have only one system wide Python Interpreter. Also makes sharing DB connections and so much easier since you can just keep lots of globals around.
And that's on Solaris, where worker isn't default.
Oh, and mod_deflate is nice too.
Musicians don't die. They just decompose.