[OpenSTA-devel] [ opensta-Bugs-1389081 ] Gateway does not munge HTTPS URLs in CSS content

[SourceForge.net <no...@so...>]

Bugs item #1389081, was opened at 2005-12-23 13:56
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1389081&group_id=10857

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: HTTP Capture
Group: Behavioral
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Sutcliffe (dansut)
Assigned to: Daniel Sutcliffe (dansut)
Summary: Gateway does not munge HTTPS URLs in CSS content

Initial Comment:
While recording HTTPS traffic the gateway must
translate all HTTPS URLs in the content returned to the
client being recorded to be http://{ - this is to stop
the client attempting to make SSL/TLS connections to
the Gateway which cannot be recorded and will stop the
halt the gateway.  You can see this happen if you have
a "Unsupported protocol ..." comment in your created
script and your recording browser stops being able to
access any site.

In the OpenSTA 1.4.3 release and earlier the only
content they had this munging done was HTML and
javascript.  The most obvious other type of content
that may need munging is CSS ... but there may be others.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1389081&group_id=10857