• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: backtracking and Mac browsers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: backtracking and Mac browsers


  • Subject: Re: backtracking and Mac browsers
  • From: Patrick Robinson <email@hidden>
  • Date: Mon, 19 Apr 2004 10:16:31 -0400

On Apr 17, 2004, at 1:50 AM, Patrick Robinson wrote:
Has anyone else noticed that Mac browsers - at least Safari 1.2.1 and IE 5.2.3 - ignore all the various HTTP headers that WebObjects adds when isPageRefreshOnBacktrackEnabled() returns true? That is, when this method returns true, backtracking (or forwardtracking, for that matter) to a previously visited page is supposed to cause the browser to resubmit the HTTP request, rather than display the page from the browser's cache. It works as expected on my Windows XP machine with IE 6.0, and Netscapes 4.8 and 7.1. But the Mac browsers don't resubmit anything 'til you click on something.

What's *that* about?

I found something that at least acknowledges variant behavior between browsers, although it doesn't mention Safari:

  http://developer.apple.com/documentation/WebObjects/Web_Applications/BacktrackingAndCache/chapter_6_section_5.html#TPXREF107

Quoting from that page:
----------
 When pageRefreshOnBacktrackEnabled is set to true, backtracking should
 result in a request to the application (you should see a context ID
 line with a new context ID) when a user backtracks, although the
 actual behavior differs among various web browsers.

 In Mac OS X, web browsers that use the Gecko HTML rendering engine
 (such as Chimera and Mozilla), comply most closely to the HTTP
 specification.  Clicking the Back button causes the browser to ask
 for an updated version of an expired webpage. Other browsers, such
 as Internet Explorer and OmniWeb, behave differently: The first few
 clicks (two to three, depending on the browser) of the Back button
 reload the page from the cache.  Subsequent clicks cause the browser
 to send a request to the application.

 Notice that when the browser requests the updated version of the
 webpage from the application, the page-load counter doesn't decrease,
 but the time is updated.

 You must test your application on many configurations to ensure that
 it provides a good user experience.
----------

--
Patrick Robinson
AHNR Info Technology, Virginia Tech
email@hidden
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >backtracking and Mac browsers (From: Patrick Robinson <email@hidden>)

  • Prev by Date: Decoding Site configuration
  • Next by Date: Fwd: WORepetition not displaying
  • Previous by thread: backtracking and Mac browsers
  • Next by thread: making associations between eomodeler files
  • Index(es):
    • Date
    • Thread