firebase hosting url rewrite pattern matching
How do I rewrite urls like:
http://somedomain.com/page.html
to
http://somedomain.com/DIRECTORY/page.html
in firebase hosting. I tried this in firebase.json but didn't work.
"rewrites": [ {
"source": "/**.html",
"destination": "/DIRECTORY/**.html"
} ]
How does pattern matching work in firebase hosting config. Help would be appreciated.
firebase firebase-hosting
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
add a comment |
How do I rewrite urls like:
http://somedomain.com/page.html
to
http://somedomain.com/DIRECTORY/page.html
in firebase hosting. I tried this in firebase.json but didn't work.
"rewrites": [ {
"source": "/**.html",
"destination": "/DIRECTORY/**.html"
} ]
How does pattern matching work in firebase hosting config. Help would be appreciated.
firebase firebase-hosting
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
add a comment |
How do I rewrite urls like:
http://somedomain.com/page.html
to
http://somedomain.com/DIRECTORY/page.html
in firebase hosting. I tried this in firebase.json but didn't work.
"rewrites": [ {
"source": "/**.html",
"destination": "/DIRECTORY/**.html"
} ]
How does pattern matching work in firebase hosting config. Help would be appreciated.
firebase firebase-hosting
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
How do I rewrite urls like:
http://somedomain.com/page.html
to
http://somedomain.com/DIRECTORY/page.html
in firebase hosting. I tried this in firebase.json but didn't work.
"rewrites": [ {
"source": "/**.html",
"destination": "/DIRECTORY/**.html"
} ]
How does pattern matching work in firebase hosting config. Help would be appreciated.
firebase firebase-hosting
firebase firebase-hosting
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
asked Nov 23 '18 at 15:57
saibbywebsaibbyweb
8261618
8261618
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
From the Firebase Hosting documentation on rewrites:
The rewrites attribute contains an array of rewrite rules, where each rule must include:
A
sourcespecifying a glob pattern
A
destination, which is a local file that must exist
So it looks like you can only rewrite to a specific, existing file, not to another wildcard.
You could consider using redirects instead, since those do support dynamic segments in their destination URL.
"redirects": [ {
"source": "/:page*",
"destination": "http://somedomain.com/DIRECTORY/:page",
"type": 301
}]
This sends a redirect instruction back to the client, so they will be able to see what the final path is.
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53449709%2ffirebase-hosting-url-rewrite-pattern-matching%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the Firebase Hosting documentation on rewrites:
The rewrites attribute contains an array of rewrite rules, where each rule must include:
A
sourcespecifying a glob pattern
A
destination, which is a local file that must exist
So it looks like you can only rewrite to a specific, existing file, not to another wildcard.
You could consider using redirects instead, since those do support dynamic segments in their destination URL.
"redirects": [ {
"source": "/:page*",
"destination": "http://somedomain.com/DIRECTORY/:page",
"type": 301
}]
This sends a redirect instruction back to the client, so they will be able to see what the final path is.
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
add a comment |
From the Firebase Hosting documentation on rewrites:
The rewrites attribute contains an array of rewrite rules, where each rule must include:
A
sourcespecifying a glob pattern
A
destination, which is a local file that must exist
So it looks like you can only rewrite to a specific, existing file, not to another wildcard.
You could consider using redirects instead, since those do support dynamic segments in their destination URL.
"redirects": [ {
"source": "/:page*",
"destination": "http://somedomain.com/DIRECTORY/:page",
"type": 301
}]
This sends a redirect instruction back to the client, so they will be able to see what the final path is.
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
add a comment |
From the Firebase Hosting documentation on rewrites:
The rewrites attribute contains an array of rewrite rules, where each rule must include:
A
sourcespecifying a glob pattern
A
destination, which is a local file that must exist
So it looks like you can only rewrite to a specific, existing file, not to another wildcard.
You could consider using redirects instead, since those do support dynamic segments in their destination URL.
"redirects": [ {
"source": "/:page*",
"destination": "http://somedomain.com/DIRECTORY/:page",
"type": 301
}]
This sends a redirect instruction back to the client, so they will be able to see what the final path is.
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
From the Firebase Hosting documentation on rewrites:
The rewrites attribute contains an array of rewrite rules, where each rule must include:
A
sourcespecifying a glob pattern
A
destination, which is a local file that must exist
So it looks like you can only rewrite to a specific, existing file, not to another wildcard.
You could consider using redirects instead, since those do support dynamic segments in their destination URL.
"redirects": [ {
"source": "/:page*",
"destination": "http://somedomain.com/DIRECTORY/:page",
"type": 301
}]
This sends a redirect instruction back to the client, so they will be able to see what the final path is.
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
edited Nov 23 '18 at 16:52
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
answered Nov 23 '18 at 16:07
Frank van PuffelenFrank van Puffelen
236k29382408
236k29382408
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
add a comment |
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
I had seen it earlier but couldn't exactly figure out how it would work in my case. I gave it a try and came up with the config posted in my question which isn't working. Can you post the pattern for my problem (in question)?
– saibbyweb
Nov 23 '18 at 16:35
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
Oh! I got it now.
– saibbyweb
Nov 23 '18 at 16:38
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53449709%2ffirebase-hosting-url-rewrite-pattern-matching%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
