Azure CDN session issue backend application gateway
I have setup jira with CDN (premium Verzion) and application gateway. All request serve from CDN. I have identify the actual issue. Issue was Application gateway consider CDN ip as client ip, So each request AG providing different cookie token. I need Rule engine for forwarding client ip only to AG.
Clietn -> CDN -> Application Gateway -> Jira node
azure jira azure-cdn
add a comment |
I have setup jira with CDN (premium Verzion) and application gateway. All request serve from CDN. I have identify the actual issue. Issue was Application gateway consider CDN ip as client ip, So each request AG providing different cookie token. I need Rule engine for forwarding client ip only to AG.
Clietn -> CDN -> Application Gateway -> Jira node
azure jira azure-cdn
add a comment |
I have setup jira with CDN (premium Verzion) and application gateway. All request serve from CDN. I have identify the actual issue. Issue was Application gateway consider CDN ip as client ip, So each request AG providing different cookie token. I need Rule engine for forwarding client ip only to AG.
Clietn -> CDN -> Application Gateway -> Jira node
azure jira azure-cdn
I have setup jira with CDN (premium Verzion) and application gateway. All request serve from CDN. I have identify the actual issue. Issue was Application gateway consider CDN ip as client ip, So each request AG providing different cookie token. I need Rule engine for forwarding client ip only to AG.
Clietn -> CDN -> Application Gateway -> Jira node
azure jira azure-cdn
azure jira azure-cdn
edited Nov 21 '18 at 8:38
CHEEKATLAPRADEEP-MSFT
2,084413
2,084413
asked Nov 21 '18 at 5:19
ThamotharanThamotharan
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You should have an option to indicate Verizon to add a header with the client's IP Address. Take a look at Verizon-specific HTTP headers for Azure CDN rules engine, specifically, on the X-Forwarded-For
header.
Hope it helps!
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
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%2f53405672%2fazure-cdn-session-issue-backend-application-gateway%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
You should have an option to indicate Verizon to add a header with the client's IP Address. Take a look at Verizon-specific HTTP headers for Azure CDN rules engine, specifically, on the X-Forwarded-For
header.
Hope it helps!
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
add a comment |
You should have an option to indicate Verizon to add a header with the client's IP Address. Take a look at Verizon-specific HTTP headers for Azure CDN rules engine, specifically, on the X-Forwarded-For
header.
Hope it helps!
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
add a comment |
You should have an option to indicate Verizon to add a header with the client's IP Address. Take a look at Verizon-specific HTTP headers for Azure CDN rules engine, specifically, on the X-Forwarded-For
header.
Hope it helps!
You should have an option to indicate Verizon to add a header with the client's IP Address. Take a look at Verizon-specific HTTP headers for Azure CDN rules engine, specifically, on the X-Forwarded-For
header.
Hope it helps!
answered Nov 21 '18 at 8:10
Itay PodhajcerItay Podhajcer
1,869312
1,869312
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
add a comment |
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
Thanks, I tried that option. but application gateway providing different cookie. I tried to connect the application gateway directly and all cookies comes under "request cookie" and its working without issues. But when I connect via CDN, application gateway cookies are getting set in "response cookie" (Think so application gateway considers each request from CDN as client IP's after including x-forwarded-for). Still issue not fixed
– Thamotharan
Nov 21 '18 at 11:49
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53405672%2fazure-cdn-session-issue-backend-application-gateway%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