I have a problem in IE 6.0 with SV2
I want to Quote this on your Site, but i was not able to find out the correct path. Please assist on the same. Or else following is my issue.

I have a Web based project going on. For my users who will be acessing thru internet i am using HTTPS. Few of my clients when they type in the URL and press enter they get the following message

ERROR
The requested URL could not be retrieved


But on the next moment when they refresh the page they get the access to the mentioned URL.. But this is affecting the offline module of this system as it does'nt have the refresh facility.
This is def not a server end problem as i can access the site from different PC having XP SV2.
I ave tried most of the IE options but not yet able to resolve the issue.
Can you provide any assistance/help in resolving this.

Dani AI

Generated

Symptom analysis: the intermittent "The requested URL could not be retrieved" behavior on only some XP SP2 clients usually points to a client-side/proxy/cache interaction rather than your server. The fact a manual refresh immediately succeeds suggests an HTTPS cache or proxy handshake issue, an IE caching policy, or SSL interception by AV/endpoint software. That fits 's note that only some machines fail and explains why the offline module—if it depends on a cached copy—can't find a usable page until a fresh fetch occurs.

Practical troubleshooting (order matters):

  1. When the error appears, inspect the error page source or headers (or run a quick capture with Fiddler) to see which device generated the message (proxy name, ISA, Squid, etc.). That immediately shows whether a gateway/proxy is returning the error.
  2. Compare the affected machine's Internet Options with a working one. Key items to check: proxy settings (Connections > LAN Settings), Advanced > Security setting "Do not save encrypted pages to disk" (if checked, HTTPS will not be cached), and Browsing History > Settings ("Check for newer versions of stored pages").
  3. Temporarily disable AV/endpoint SSL scanning on the client and retry. Many AV products insert a local proxy and can cause intermittent failures on the first SSL handshake.
  4. If a proxy is in use, try toggling "Use HTTP 1.1 through proxy" or test bypassing the proxy (with caution and admin approval) to isolate it.

If those steps isolate the culprit, fix client policy or change the offline module so it prefetches or explicitly stores required pages (or signs them) rather than relying on implicit HTTPS caching. Avoid reinstalling the OS as a first step — as discovered it can work but is usually unnecessary. For deeper faults, a packet capture from both a failing and a working client will show where the connection is dropping.

Recommended Answers

All 5 Replies

I had the same error. I was able to eliminate it only when I've reinstall the system (win xp).
Maybe there are other simple ways - this is the one that i've found and worked.


dr. Steven Dale
oncologist

Could it be a problem with the cached version of the site. When they finally arrive at your site, ask them to press Ctrl+F5. This not only refreshes the page, but the cached / offline copy of the site.

May or may not help.

This can be a option , but i was looking for a better one. I suppose there is some cache setting or some IE setting, which is causing this problem to the clients. I am looking for such exact solution.
Thanks anyways. Do reply if you ome across some other solution . If i do , i will post it across

Something is wrong with the website, not your computer

If the prolem would have been w.r.t the site , then every client machine sould have thrown the error. But this is not the case . On some of the client machines this is working absolutely fine.
Also some one suggested Ctl+F5. This advantage is not available in the Offline module.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.