Re: MSIE is not the postman
Re: MSIE is not the postman
- Subject: Re: MSIE is not the postman
- From: Thomas <email@hidden>
- Date: Fri, 11 May 2007 17:30:07 +1000
Alexander has noticed something important: two different Expires:
headers. But where do they come from? I do not do anything special in
appendToResponse anywhere, and don't do any setHeader() stuff.
But I'm now using Project Wonder, and maybe that does it. I can't
find it in the documentation, but it's late in the day...
Any help would be appreciated. This double-submission by the browser
is causing all kinds of problems.
Regards
Thomas
On 10/05/2007, at 17:49, Alexander Spohr wrote:
Am 09.05.2007 um 22:25 schrieb Thomas:
curl -v http://stage.thewoodworks.com.au/product/products/1000025/
SCROLL+SAWS/M0239.html
* About to connect() to stage.thewoodworks.com.au port 80
* Trying 202.125.168.160... * connected
* Connected to stage.thewoodworks.com.au (202.125.168.160) port 80
> GET /product/products/1000025/SCROLL+SAWS/M0239.html HTTP/1.1
User-Agent: curl/7.13.1 (powerpc-apple-darwin8.0) libcurl/7.13.1
OpenSSL/0.9.7l zlib/1.2.3
Host: stage.thewoodworks.com.au
Pragma: no-cache
Accept: */*
< HTTP/1.1 200 Apple
< Date: Wed, 09 May 2007 20:06:52 GMT
< Server: Apache/1.3.33 (Darwin) mod_jk/1.2.6 DAV/1.0.3 mod_ssl/
2.8.24 OpenSSL/0.9.7l PHP/4.4.4
< cache-control: private, no-cache, no-store, must-revalidate, max-
age=0
< expires: Mon, 07-May-2007 19:45:15 GMT
< pragma: no-cache
< set-cookie: wosid=2aqsarrQxIE0HqVfAE72qw; version="1"; path=/
< Cache-Control: max-age=60
< Expires: Wed, 09 May 2007 20:07:52 GMT
< content-length: 11882
< Connection: close
< Content-Type: text/html; charset=UTF-8
Just a guess: You have two different Expires-headers.
I do remember having problems with two content-length headers.
If its not that, I can only guess a problem in one of the
JavaScripts or something like it.
Regards,
atze
I am having a problem with MSIE 7 that does not happen in any real
browser.
There is a direct action link that selects a product. The direct
action ends in
.../groupcode/productcode.html
The direct action selects the product and displays the page with the
product details. But when you click on the link in MSIE, it sends TWO
requests to the server: the proper direct action with the full URL,
followed by another one that is just
.../groupcode/
But this second request is not displayed, only the first one is.
It just so happens that this direct action clears the selected
product in the session, so any component actions in the detail page,
like adding to the shopping cart, fail because there is no selected
product. And of course the page that results when you click "add to
cart" shows the list of products in the group, instead of the detail
page, because the selected product has been cleared.
Other browsers work properly, but with some odd behaviour:
- Safari sends one request.
- Camino 1.0 and Firefox 2 both send TWO requests, but they are both
the full URLs.
Anybody have any ideas? This is driving me nuts. The site is a work
in progress, but it won't go live with problems like this.
For those who are curious, the work-in-progress page with the problem
is:
http://stage.thewoodworks.com.au/product/products/1000025/SCROLL
+SAWS.html
Clicking on "more info" on any product gives the problem.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden