SitePoint.com

Floezen · Nov 8, 2009, 13:58

Hi,

I am having a very strange problem: I have a field in my db where I store to content of emails base64_encoded.
When I read this table and decode the content I can echo it "human readable", but if I try to update the table with exact the same content it stays encoded...

The second strange thing is, that this applies to around 80% of the rows, but not all.

Here is the code:

PHP Code:


$get_decoded_body_data = mysql_query("select id, content from ".$prefix."_bounced_mails", $dbi);

while(list($decoded_id, $decoded_body_data)=mysql_fetch_row($get_decoded_body_data)) {

//decode  $decoded_body_data

$new_content = base64_decode($decoded_body_data);

//Echo readable text

echo $new_content<br />";

//Insert readable text into db

mysql_query ("update ".$prefix."_bounced_mails set content='$new_content' WHERE id='$decoded_id'", $dbi);

}

Encoded rows which start with "SGkuIFRoa" will stay encoded, others are readable after the update.

Notice: When echoing $new_content everything is decoded!

I really don't have a clue what's going on. Please help!

Regards
Florian

Shrapnel_N5 · Nov 8, 2009, 14:19

ever heard of mysql_real_escape_string()?

Floezen · Nov 10, 2009, 11:42

apparently not...

Thanx for that tip!

Shrapnel_N5 · Nov 10, 2009, 12:01

must be used every time you place data into query.
wonder, how lived without id before

cranial-bore · Nov 10, 2009, 16:20

To be clear Floezen, you should be escaping data used in a query whenever it may have come from a user (GET, POST, COOKIE), or another external source, or even your own data if it could contain funky characters.

Nov 8, 2009, 13:58	#1
Floezen SitePoint Addict Join Date: Feb 2003 Location: Berlin Posts: 315	Unable to insert base64_decode data in mySQL Hi, I am having a very strange problem: I have a field in my db where I store to content of emails base64_encoded. When I read this table and decode the content I can echo it "human readable", but if I try to update the table with exact the same content it stays encoded... The second strange thing is, that this applies to around 80% of the rows, but not all. Here is the code: PHP Code: `$get_decoded_body_data = mysql_query("select id, content from ".$prefix."_bounced_mails", $dbi); while(list($decoded_id, $decoded_body_data)=mysql_fetch_row($get_decoded_body_data)) { //decode $decoded_body_data $new_content = base64_decode($decoded_body_data); //Echo readable text echo $new_content<br />"; //Insert readable text into db mysql_query ("update ".$prefix."_bounced_mails set content='$new_content' WHERE id='$decoded_id'", $dbi); }` Encoded rows which start with "SGkuIFRoa" will stay encoded, others are readable after the update. Notice: When echoing $new_content everything is decoded! I really don't have a clue what's going on. Please help! Regards Florian

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Nov 8, 2009, 14:19	#2
Shrapnel_N5 SitePoint Evangelist Join Date: Oct 2009 Posts: 464	ever heard of mysql_real_escape_string()?

Nov 10, 2009, 11:42	#3
Floezen SitePoint Addict Join Date: Feb 2003 Location: Berlin Posts: 315	apparently not... Thanx for that tip!

Nov 10, 2009, 12:01	#4
Shrapnel_N5 SitePoint Evangelist Join Date: Oct 2009 Posts: 464	must be used every time you place data into query. wonder, how lived without id before

Nov 10, 2009, 16:20	#5
cranial-bore SitePoint Wizard Join Date: Jan 2002 Location: Australia Posts: 2,092	To be clear Floezen, you should be escaping data used in a query whenever it may have come from a user (GET, POST, COOKIE), or another external source, or even your own data if it could contain funky characters.