Hi Jim,
I guess I misinterpret the meaning of this <meta>. I hope it will set
the Expect:100-continue in the http request.
What I try to do is this:
I have an application to upload some files from browser to Web server.
I am using IBM HTTP Server/WebSphere 3.5 and the upload work with only
problem -- it can't forward to a predefine error page if file is over
our file size limit. Instead, it will give you "Can't find server"
error. According IBM, this is known bug and they have a fix. But their
fix will wait for the file to be transmitted completed before
forwarding to a error page. So, if you have a hugh file, it will take
a very long time before saying the file is too big. That is not
acceptable and waste a lot of network bandwidth.
Again, IBM says we may able use Expect/Continue in HTTP 1.1 and they
do a simple test with telnet and it should OK. But, of course, we are
not using telnet and with Internet Explorer and HTML, I just wonder
how to set Expect/Continue in HTTP request header. After going thru
HTML4.0 spec, I thought <META> may be able to do what I want.
Apparent, my understanding is incorrect.
Regards,
Mak
Jim Dabell <ji********@jimdabell.com> wrote in message news:<6Z********************@giganews.com>...
Mak wrote:
I try set the Expect: 100-continue in my request to server. The way I
do it is by setting :
<META http-equiv="Expect" content="100-continue">
in my html page. But, it does not do the trick. Can anyone let me know
how to do that ?
Using <meta> elements to emulate real HTTP headers usually fails. However,
even if it worked as designed, the <meta> element isn't what you need -
it's for response headers (headers that the server sends to the client).
There isn't anything you can put in an HTML document that will tell a
user-agent to send certain headers.
What are you trying to accomplish?