View Issue Details

Jump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0002068OXID eShop (all versions)1. ----- eShop frontend -----public2010-08-27 15:462012-12-10 14:38
Reportersventietje Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status resolvedResolutionduplicate 
PlatformApacheOSSLESOS Version11
Product Version4.3.2 revision 27884 
Summary0002068: sAltImage and SSL
Descriptionhi,

if $sAltImage is used an SSL is on, https works for nearly fine for all images except the mini_basket. the session stores the ssl and the non ssl-url of the image using oxbasketitem. therefore it resolves the urls from oxarticle. oxarticle does the following:

        $this->dabsimagedir = $myConfig->getPictureDir( false ); //$sThisShop
        $this->nossl_dimagedir = $myConfig->getPictureUrl( null, false, false, null, $sThisShop ); //$sThisShop

Steps To Reproduce1. set sAltimage
2. set ssl
Additional Informationthe problem is the method oxconfig::getPictureURL:

        if ( $sAltUrl = $this->getConfigParam( 'sAltImageDir' ) ) {

            if ( $this->isSsl()) {
                $sAltUrl = str_replace( 'http://', 'https://', $sAltUrl );
            }

            if ( !is_null( $sFile ) ) {
                $sAltUrl .= $sFile;
            }

            return $sAltUrl;
        }

the $blSSL - param is totally ignored in case of sAltImage. the part
            if ( $this->isSsl()) {
                $sAltUrl = str_replace( 'http://', 'https://', $sAltUrl );
            }

should be replace by
            if ( $this->isSsl() || $blSSL === true) {
                $sAltUrl = str_replace( 'http://', 'https://', $sAltUrl );
            }
TagsNo tags attached.
Theme
BrowserAll
PHP Versionany
Database Version5.0.67

Relationships

duplicate of 0001678 resolvedvilma_liorensaityte $this->sAltImageDir='' causes warning due to non-ssl connection 

Activities

dainius.bigelis

2010-08-27 16:58

reporter   ~0003449

Reminder sent to: sventietje

Hi,

Thank you very much for your report, effort, code snippets and suggested fix. There was a similar bug reported some time earlier, but with lower priority. I increased the priority and severity, so this issue will be investigated and will be fixed soon.
This entry will be closed. But the reference to this will be included in the older bug, as it contains valuable details.

Best regards,