2001-09-29 00:14:13 +04:00
|
|
|
/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
|
2012-05-21 15:12:37 +04:00
|
|
|
/* This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
1999-11-23 15:13:33 +03:00
|
|
|
|
|
|
|
#ifndef nsResProtocolHandler_h___
|
|
|
|
#define nsResProtocolHandler_h___
|
|
|
|
|
2015-07-17 01:50:07 +03:00
|
|
|
#include "SubstitutingProtocolHandler.h"
|
|
|
|
|
1999-11-23 15:13:33 +03:00
|
|
|
#include "nsIResProtocolHandler.h"
|
2003-09-13 21:55:56 +04:00
|
|
|
#include "nsInterfaceHashtable.h"
|
2000-08-22 10:09:52 +04:00
|
|
|
#include "nsWeakReference.h"
|
2004-12-02 09:59:34 +03:00
|
|
|
#include "nsStandardURL.h"
|
|
|
|
|
2015-07-17 01:50:07 +03:00
|
|
|
struct SubstitutionMapping;
|
|
|
|
class nsResProtocolHandler final : public nsIResProtocolHandler,
|
|
|
|
public mozilla::SubstitutingProtocolHandler,
|
|
|
|
public nsSupportsWeakReference
|
1999-11-23 15:13:33 +03:00
|
|
|
{
|
|
|
|
public:
|
2015-07-17 01:50:07 +03:00
|
|
|
NS_DECL_ISUPPORTS_INHERITED
|
1999-11-23 15:13:33 +03:00
|
|
|
NS_DECL_NSIRESPROTOCOLHANDLER
|
|
|
|
|
2015-07-17 01:50:07 +03:00
|
|
|
NS_FORWARD_NSIPROTOCOLHANDLER(mozilla::SubstitutingProtocolHandler::)
|
2001-09-15 01:19:41 +04:00
|
|
|
|
2015-07-17 01:50:07 +03:00
|
|
|
nsResProtocolHandler()
|
2015-07-20 09:06:52 +03:00
|
|
|
: SubstitutingProtocolHandler("resource", URI_STD | URI_IS_UI_RESOURCE | URI_IS_LOCAL_RESOURCE,
|
|
|
|
/* aEnforceFileOrJar = */ false)
|
2015-07-17 01:50:07 +03:00
|
|
|
{}
|
2010-03-11 08:33:00 +03:00
|
|
|
|
2015-07-17 01:50:07 +03:00
|
|
|
nsresult Init();
|
2002-08-15 22:38:46 +04:00
|
|
|
|
Bug 1225384 - Change how the default resource "host names" are handled. r=michal
The meaning of resource:///, resource://app/ and resource://gre/ needs to
remain constant. Unfortunately, the model of the resource protocol handler
is that it is possible to set substitutions that change their meaning.
So, we forbid setting overwriting the substitutions for those three
special "host names".
Unfortunately, with e10s, the full list of substitutions is also sent to
the content process, which then sets substitutions, making it harder to
know in which cases SetSubstitution is valid for those three "host names"
or not.
So instead of trying to find the right heuristics, use the recently added
SubstitutingProtocolHandler::ResolveSpecialCases API to handle the three
"host names" instead of storing them as "normal" substitutions.
Still actively reject SetSubstitution with the three special "host names"
so as to find issues such as bug 1224000 instead of allowing the chrome
manifest entry and have it silently ignored.
Additionally, make GetSubstitution return the URIs for the three special
"host names" through GetSubstitutionInternal, replacing what was originally
added in bug 257162. Those changes from bug 257162 relied on the
resource:app string being handled by nsXREDirProvider::GetFile, but that was
removed in bug 620931, effectively making that code now in
GetSubstitutionInternal useless.
2015-11-17 11:21:03 +03:00
|
|
|
NS_IMETHOD SetSubstitution(const nsACString& aRoot, nsIURI* aBaseURI) override;
|
|
|
|
|
|
|
|
NS_IMETHOD GetSubstitution(const nsACString& aRoot, nsIURI** aResult) override
|
|
|
|
{
|
|
|
|
return mozilla::SubstitutingProtocolHandler::GetSubstitution(aRoot, aResult);
|
|
|
|
}
|
|
|
|
|
|
|
|
NS_IMETHOD HasSubstitution(const nsACString& aRoot, bool* aResult) override
|
|
|
|
{
|
|
|
|
return mozilla::SubstitutingProtocolHandler::HasSubstitution(aRoot, aResult);
|
|
|
|
}
|
|
|
|
|
|
|
|
NS_IMETHOD ResolveURI(nsIURI *aResURI, nsACString& aResult) override
|
|
|
|
{
|
|
|
|
return mozilla::SubstitutingProtocolHandler::ResolveURI(aResURI, aResult);
|
|
|
|
}
|
|
|
|
|
2015-07-17 01:50:07 +03:00
|
|
|
protected:
|
|
|
|
nsresult GetSubstitutionInternal(const nsACString& aRoot, nsIURI** aResult) override;
|
|
|
|
virtual ~nsResProtocolHandler() {}
|
Bug 1225384 - Change how the default resource "host names" are handled. r=michal
The meaning of resource:///, resource://app/ and resource://gre/ needs to
remain constant. Unfortunately, the model of the resource protocol handler
is that it is possible to set substitutions that change their meaning.
So, we forbid setting overwriting the substitutions for those three
special "host names".
Unfortunately, with e10s, the full list of substitutions is also sent to
the content process, which then sets substitutions, making it harder to
know in which cases SetSubstitution is valid for those three "host names"
or not.
So instead of trying to find the right heuristics, use the recently added
SubstitutingProtocolHandler::ResolveSpecialCases API to handle the three
"host names" instead of storing them as "normal" substitutions.
Still actively reject SetSubstitution with the three special "host names"
so as to find issues such as bug 1224000 instead of allowing the chrome
manifest entry and have it silently ignored.
Additionally, make GetSubstitution return the URIs for the three special
"host names" through GetSubstitutionInternal, replacing what was originally
added in bug 257162. Those changes from bug 257162 relied on the
resource:app string being handled by nsXREDirProvider::GetFile, but that was
removed in bug 620931, effectively making that code now in
GetSubstitutionInternal useless.
2015-11-17 11:21:03 +03:00
|
|
|
|
2016-07-12 23:55:14 +03:00
|
|
|
bool ResolveSpecialCases(const nsACString& aHost,
|
|
|
|
const nsACString& aPath,
|
|
|
|
const nsACString& aPathname,
|
Bug 1225384 - Change how the default resource "host names" are handled. r=michal
The meaning of resource:///, resource://app/ and resource://gre/ needs to
remain constant. Unfortunately, the model of the resource protocol handler
is that it is possible to set substitutions that change their meaning.
So, we forbid setting overwriting the substitutions for those three
special "host names".
Unfortunately, with e10s, the full list of substitutions is also sent to
the content process, which then sets substitutions, making it harder to
know in which cases SetSubstitution is valid for those three "host names"
or not.
So instead of trying to find the right heuristics, use the recently added
SubstitutingProtocolHandler::ResolveSpecialCases API to handle the three
"host names" instead of storing them as "normal" substitutions.
Still actively reject SetSubstitution with the three special "host names"
so as to find issues such as bug 1224000 instead of allowing the chrome
manifest entry and have it silently ignored.
Additionally, make GetSubstitution return the URIs for the three special
"host names" through GetSubstitutionInternal, replacing what was originally
added in bug 257162. Those changes from bug 257162 relied on the
resource:app string being handled by nsXREDirProvider::GetFile, but that was
removed in bug 620931, effectively making that code now in
GetSubstitutionInternal useless.
2015-11-17 11:21:03 +03:00
|
|
|
nsACString& aResult) override;
|
|
|
|
|
|
|
|
private:
|
|
|
|
nsCString mAppURI;
|
|
|
|
nsCString mGREURI;
|
1999-11-23 15:13:33 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
#endif /* nsResProtocolHandler_h___ */
|