Project

General

Profile

Actions

Bug #25986

closed

CE Mailform does not respect https protocol

Added by Marc Wöhlken over 13 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Content Rendering
Target version:
-
Start date:
2011-04-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When using a Mailform CE pointing to a https enforced target page (Tab behavior -> Use protocol = https) the rendered html for the mail form does not point to the https-protected page. Instead a relative URL is created which leaves out the trasmission protocol.

Expected behavior: Mailform action points to https://www.example.com/index.php?id=XYZ
Actual behavior: Mailform action points to unsecured http://www.example.com/index.php?id=XYZ

Actions #1

Updated by Helmut Hummel over 13 years ago

I don't understand the problem here. If the mailform content element creates a relative URL, everything should be fine. The page will only be available through https and the relative URL then also uses this protocol.

Actions #2

Updated by Marc Wöhlken over 13 years ago

Problem is:
Page A: http-based, contains mailform, target page: page B
Page B: https-enforced via page properties

The mailform on page A gets an action pointing to page B. That action is a simple relative path like /index.php?id=XYZ as the baseref for page A uses http-protocol.
This means the target page can only be viewed using https and thus the mailform will not work and send unencrypted data which is highly unexpected.

Actions #3

Updated by Alexander Opitz over 10 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.3)?

Actions #4

Updated by Marc Wöhlken over 10 years ago

Alexander Opitz wrote:

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.3)?

Problem is fixed using version 6.2.3. IMHO the ticket can be closed.

Actions #5

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed
  • Assignee deleted (Susanne Moog)
Actions

Also available in: Atom PDF