Bug #44108

extjs core runs http requests to www.extjs.com (www.sencha.com)

Added by Joachim Mathes over 8 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-12-19
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hi Core-Team,

there are obviously http requests from within the extjs framework to the website of the extjs project. In ext-all-debug.js and thus in ext-all.js an image is requested by calling http://www.extja.com/s.gif (http://www.sencha.com/s.gif) depending on the browser. This not only leads to a security warning in IE7, if the website runs in https mode. Furthermore it is a severe security issue in general. Since extjs is part of the TYPO3 core, can you bring the extjs project to remove these calls from the extjs-core?

Best regards
Joachim

#1

Updated by Jigal van Hemert over 8 years ago

  • Status changed from New to Accepted

In the PageRenderer it seems that Ext.BLANK_IMAGE_URL is set to the blank image in the TYPO3 installation. Maybe we can this on a more global level?

#2

Updated by Joachim Mathes over 8 years ago

Thanks for this hint! This will help us with our extension, which uses the sencha tree widget in an AJAX context. Nevertheless it would be great, if you find a more global level.

#3

Updated by Helmut Hummel over 8 years ago

  • Status changed from Accepted to Needs Feedback

Jigal van Hemert wrote:

In the PageRenderer it seems that Ext.BLANK_IMAGE_URL is set to the blank image in the TYPO3 installation. Maybe we can this on a more global level?

So is it a problem in the usage of ExtJS in TYPO3 itself or only if the pageRenderer is not used?

#4

Updated by Joachim Mathes over 8 years ago

In my case it's the usage of EXTJS in a TYPO3 extension. But we managed to solve the problem like it was solved in the pageRenderer.

#5

Updated by Helmut Hummel over 8 years ago

  • Status changed from Needs Feedback to Rejected

Joachim Mathes wrote:

In my case it's the usage of EXTJS in a TYPO3 extension. But we managed to solve the problem like it was solved in the pageRenderer.

OK, so it's no TYPO3 Core problem

Also available in: Atom PDF