My Application doesnt work in Netscape 4.79

osnewbie2004

Hello!

I have an order system which works fine with IE versions
but does not work well with Netscape Ver 4.79(this is what we use across campus). Basically in my app a user chooses
a delivery date like Jan 27,2005 and a Building Name like Building A and then hits submit. After submitting it goes to a new page
with corresponding text boxes of delivery date and building name filled in ...then user enters the quantitys of items needed...and hits a submit...thats it a simple app...

However, in Netscape ver 4.79 after a user chooses delivery date and a building name like Building A and submits...in the next page
delivery date field is empty and building name is partially filled
like Building only instead of Building A. There is one exception to this If building Name is Oak...not Oak A or something like that...
then every thing works fine ...I wonder why this single space(between Oak and A) is creating such a havoc for me...any immediate help is highly appreciated...

Thanks,
Sean

Roger_Ramjet

How are you passing the data to the target script? In the uri? if so it needs to be rawurlencode 'ed so that spaces become %20 . This is the usual reason for data being truncated on a space.rawurlencode

osnewbie2004

Hello! Roger,

Thanks! so much for a prompt reply...below is the code I use to pass on the values of delivery date & home name.

<input name="txtDeliveryDate" type="text" value="<?php echo $_REQUEST['DeliveryDate'];?>" readonly="true">

<input name="txtHome" type="text" value="<?php echo $_REQUEST['HomeName'];?>" readonly="true">

Pls let me know how do I oversome the space problem in Netscape v 4.79.

Thanks,
Sean

Roger_Ramjet

Look at the source code that the browser is receiving when the page is displayed. Post it here if you want. It's too long since NS 4.1 to begin to think what the problem is.

osnewbie2004

<html>
<head>
<title>Dietary New Order Page</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>

<form name="form1" method="POST" action="/Dietary/new_order.php?HomeName=Oak">
Please
Enter Your Order
Delivery Date: 
<input name="txtDeliveryDate" type="text" value="" readonly="true">

Home Name: 
<input name="txtHome" type="text" value="Oak" readonly="true">

Food
Items

Unit&nbsp;  Quantity&nbsp;</font><font color="#990000" size="4">&nbsp;&nbsp;</font><font size="4">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font> 
&nbsp;&nbsp;&nbsp; </strong></p>

Dairy:
Regular Milk
Gallon   </strong

<input name="txtRM" type="text" value="0" size="8" maxlength="2">
   
Skim Milk
1/2 Gallon            

Low Fat Chocolate
Milk 1/2 
Gallon  

Bread:
Whole Wheat Bread Loaf    
<input name="txtWWB" type="text" value="0" size="8" maxlength="2">

Order Requested By:
<input name="txtSubmittedby" type="text" size="40" maxlength="40" echo "">


<input type="submit" name="Submit" value="Submit Order">

 
<input type="hidden" name="MM_insert" value="form1">
</form>
 
</body>
</html>

If you notice actually the home name should be Oak A...not just Oak...

Look at the source code below....this home name is Cypress it has no suffix...hence this works fine....why does a suffix with a space makes such a difference...

<html>
<head>
<title>Dietary New Order Page</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>

<form name="form1" method="POST" action="/Dietary/new_order.php?HomeName=Cypress&DeliveryDate=2005-02-24" onSubmit="return validateForm(this);">
Please
Enter Your Order
Delivery Date: 
<input name="txtDeliveryDate" type="text" value="2005-02-24" readonly="true">
strong>
Home Name: 
<input name="txtHome" type="text" value="Cypress" readonly="true">

Roger again thanks so much for replying promptly.

Thanks,
Sean

Roger_Ramjet

Yes. It's the uri string. Read the manual for rawurlencode
and urlencode if you want to know why. Basically, all data included in a URL should be encoded, regardless of whether it has embedded spaces etc. Read the manual and decide which one best suits your needs in a particular case.

The fact that some browsers work and some don't is because they implement the various RFCs and standards differently.