Project

General

Profile

Actions

Bug #85657

closed

Accessing the standalone install tool gives a 401 error in the browser console

Added by Markus Klein over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2018-07-26
Due date:
% Done:

0%

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

Description

Accessing the install tool in standalone mode gives an error in the browser console

typo3/install.php?install[controller]=layout&install[action]=executeSilentConfigurationUpdate&_=1532606775517 401 (Unauthorized)

This does not cause any error in terms of functionality, but is a bit unclean in terms of coding.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Task #86347: Improve install tool loading messageClosed2018-09-21

Actions
Related to TYPO3 Core - Bug #86259: Install Tool does not provide a loading indicatorClosedMarkus Klein2018-09-15

Actions
Actions #1

Updated by Susanne Moog over 5 years ago

  • Target version changed from 9 LTS to Candidate for patchlevel
Actions #2

Updated by Markus Klein over 5 years ago

  • Status changed from New to Closed
  • Target version deleted (Candidate for patchlevel)

Seems to be fixed

Actions #3

Updated by Christian Kuhn over 5 years ago

actually, that is NOT fixed: this happens only if you are not logged in (standalone mode and no open be user session), so if the 'enable_install_tool file' is shown.

meanwhile, this is a 403, btw.

i had a look at this, and actually, i'd keep it like that: the simple strategy in the routing is: try to load the tool and if a 403 comes in (user not logged in), then redirect to login/enable_install_tool view. it's just that the silent upgrader is the first think that is tried, so that is the one that fails if you're not logged in.
this strategy is quite straight and saves us from a generic "do i have a session?" ajax call in front that would be performed every single click.
there is also nothing bad with receiving a 403 and then acting upon, see handleAjaxError() in router.js that has been designed to take care of that.

Actions #4

Updated by Christian Kuhn over 5 years ago

  • Related to Task #86347: Improve install tool loading message added
Actions #5

Updated by Christian Kuhn over 5 years ago

  • Related to Bug #86259: Install Tool does not provide a loading indicator added
Actions

Also available in: Atom PDF