Bug #2325

Installer fails .htaccess detection on our server because we use http authentication

Added by Anonymous almost 13 years ago. Updated over 8 years ago.

Status:NewStart date:
Priority:LowDue date:
Assignee:-% Done:


Target version:-
Google Code Legacy ID:atom-374 Tested version:
Sponsored: Requires documentation:


Google user: jack.bates

The installer check action fails and gives a warning that Options not
allowed on our server because we use HTTP authentication. Consequently it
can't get the magic words from the callback action. This is easily fixed by
adding the Authorization: HTTP header to the callback request, but how many
other such issues are there? The installer should really ape the current
request as best as possible. But I don't wanna add lots of functionality to
the custom HTTP client in the installer plugin: I think this is a job for
the sfWebBrowserPlugin. I think upgrading to the sfWebBrowserPlugin will
fix this issue. That should probably be a 1.1 task. And do it early to get
sufficient testing.

[g] Legacy categories: Installation


#1 Updated by Peter Van Garderen almost 12 years ago

  • Target version changed from Release 1.1 to Release 1.0.8

[g] Labels added: Milestone-Release-1.0.8
[g] Labels removed: Milestone-Release-1.1

#2 Updated by David Juhasz over 11 years ago

  • Target version set to Release 1.1

Bumped to Release 1.1

[g] Labels added: Milestone-Release-1.1

#3 Updated by Anonymous almost 11 years ago

  • Priority set to Low

[g] Labels added: Priority-Low

#4 Updated by Evelyn McLellan over 10 years ago

  • Target version set to Release 1.2

Moved to 1.2.

[g] Labels added: Milestone-Release-1.2

#5 Updated by David Juhasz over 9 years ago

  • Target version set to Release 1.3

Roll over to Release 1.3

[g] Labels added: Milestone-Release-1.3

Also available in: Atom PDF