Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

When my protocol changes from HTTP to HTTPS why are images/files requested again instead of being cached?

When my protocol changes from HTTP to HTTPS why are images/files requested again instead of being cached?

On replay of the script you are not only changing the protocol but also the port number. By default HTTP requests are made on port 80 and HTTPS on port 443, therefore making a request for an image etc via HTTP will actually use a URL like:

 

http://www.MyDomain:80/img/logo.gif


Whereas the HTTPS request will use a URL like:

https://www.MyDomain.com:443/img/logo.gif

 

Since these files/images are requested by differently structured URLS they are treated as different entities and therefore not cached initially. All subsequent calls for the same files will be cached (depending on user behavior specified in the profile setting) for the remainder of the test. For further clarification contact Support.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:44
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.