Ammar,
to repeat your statements :
If the comment length is more that 1249 bytes, then displaying that the
page not found!!!!
If the message is less than or equal to 1249 then no problem.
If it is "a configuration problem", as you say,
why does it work for messages less than 1249 bytes ?
Shouldn't it, in that case, *never* work ?
RFC 2616 says that 400 Bad Request means that
"the request could not be understood by the server
due to malformed syntax".
Are you modifying the headers ?
Or adding too many characters to the querystring ?
Please post the coding methods you use to store/retrieve
the comments if you want me to be able to try to help you.
I cannot help you by remote osmosis.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
=====================
Hello Juan,
The problem not in the code.
The logfile of the web server contains Protocol-Status 400,
Now I have a computer that contains a static IP that is listed in the
IP Pool of ISP firewall, and that computer is working without any
problem.
Do you think that installing SP1 of the framework V 1.1 will solve the
problem.
I think that it is a configuration problem.
Thanks a lote.
Regards,
Ammar,
how are you storing the comment ?
Please post the code you use to store the comment.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
=====================
Dear All,
I'm facing a small problem.
I have a portal web site, that contains articles, for each article,
the end user can send a comment about the article.
The problem is:
I the comment length is more that 1249 bytes, then the progress bar
of the browser will move too slow and then displaying that the page
not found!!!!
If the message is less than or equal to 1249 then no problem.