First of all, on future posts please use a title that actually describes your problem. Screaming, pleading for help and saying that you are a newbie are not very helpful in getting people with knowledge about the subject of your problem to read your post.

Second, it's a good thing you posted the output of your script. But to help you, we also need to see the input of your script as well as the script itself.

Third, a better description of what the problem is, what you expect as output as well as an example for the correct output would be very helpful.

Just post your best try. A small, runable test example is what we are looking here. Something that for example i can just copy/paste into my debugger and have it run without fiddling around too much. That way, i wouldn't waste time to get your code to run but could actually spend my time hunting the problem down and proposing a solution.

What you have to understand here is: We do this in our (unpaid) spare time. The more help you can give us, the more we are motivated to actually bother about your problem, dig into your code and help you get it fixed.

Look at it this way: Every day there are more than 20 posts asking for help (probably peaking at a hundred on very busy days). Since we do this for our fun and education, many (most) of us pick the problems that are easy to replicate on our own computers. That is not to say we only pick problems that are easy to fix - we like a challenge. But that challenge should be in finding a solution to a well specified problem. Not in trying to find out what the one asking the question is trying to ask and failing to do so.

On a side note: If you are not using strict and warnings, we are probably going to ask you to do so before touching your code. So, use strict and use warnings, and provide all the information mentioned above and you have a better change of quicker help.

BREW /very/strong/coffee HTTP/1.1
Host: goodmorning.example.com

418 I'm a teapot