On Wednesday 05 November 2003 00:04, elg3ne wrote:

> I have a db called my_directory, this table contains all the details I will
> display on the browser (104 records). Now I call all the records of the
> table using arrays. My php script has an option to add details of all the
> records on the db, so there is an option of SAVE but when I display it with
> IE & save my addtional details encoded, only 45 records is being save & the
> remaining is null, but when I use Netscape browser, all data is save. Can
> some one help me with this? thanks

there is a ph-PHP mailing list

http://lists.free.net.ph/mailman/listinfo/php

it's not very active.  but it's more  appropriate to post php problems there.
especially if  IE is involved :).

can you post a  URL we can  browse to? there's not really enough
information there  to diagnose  accurately, although i will take a stab
in  the dark :).

first a request for clarification:

  1.  when you say "save" (as in "all data is save"), do you mean 
      "i have all the data in my browser, and when i press the save
       button all the data is correctly and accurately received by the
       php script and saved to the database except when i use IE, in
       which case only 45 records out of a total of 105 are actually
       saved to the database"?  this is what i'd expect when you use 
       the word "save", but the rest of your email doesn't seem to be
       consistent with that interpretation, the context doesn't seem right.

  2.  or do you mean by "save", that "when i click on the link to
       show the data, i only see 45 records in IE even though there
       are actually 104 records in the database"?

if #1, then it might be that IE has limits on how large POST data can
be.  in a cursory look through google though, i don't see any 
documentation of such a limit (except the obligatory qualification
from W3C such that POST can be limited by the capacity of the
client computer to store data (obviously, if memory including
virtual is only 64MB and the post is 128MB, then some of it 
won't fit).  so i doubt if that's what it is.

if #2, no idea.  best if you put it online with dummy data and
post a link.  another suggestion would be, run a packet sniffer
and look at the http traffic.  see what IE is sending to the server
(it might be sending some headers that limit how much data it
can accept) and see what the server is sending (if it sends all
the data, but only half of it is showing up then it's an IE bug,
hehe, maybe it's a buffer overflow.  maybe it's exploitable.
post exploit on BugTraq and Full-Disclosure and become
famous :).


tiger

-- 
Gerald Timothy Quimpo  gquimpo*hotmail.com tiger*sni*ph
http://bopolissimus.sni.ph
Public Key: "gpg --keyserver pgp.mit.edu --recv-keys 672F4C78"

  Premature optimization is the root of all evil.
                    Donald Knuth
--
Philippine Linux Users' Group (PLUG) Mailing List
[EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
Official Website: http://plug.linux.org.ph
Searchable Archives: http://marc.free.net.ph
.
To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
.
Are you a Linux newbie? To join the newbie list, go to
http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie

Reply via email to