How to stop UrlFetchApp from turning “com.” substring into (class)
I ran an issue when trying to match a request to api.intercom.com.
api.intercom.io consistently gets changed to api.inter(class) when set as a variable and used in the UrlFetchApp call but it displays as api.intercom.io in the Logger.log output.
Screenshots:
Is there a way to stop this from happening?
javascript google-apps-script urlfetch intercom
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
asked Nov 21 '18 at 12:42
JoeJoe
1
add a comment |
I ran an issue when trying to match a request to api.intercom.com.
api.intercom.io consistently gets changed to api.inter(class) when set as a variable and used in the UrlFetchApp call but it displays as api.intercom.io in the Logger.log output.
Screenshots:
Is there a way to stop this from happening?
javascript google-apps-script urlfetch intercom
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
asked Nov 21 '18 at 12:42
JoeJoe
1
add a comment |
I ran an issue when trying to match a request to api.intercom.com.
api.intercom.io consistently gets changed to api.inter(class) when set as a variable and used in the UrlFetchApp call but it displays as api.intercom.io in the Logger.log output.
Screenshots:
Is there a way to stop this from happening?
javascript google-apps-script urlfetch intercom
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
asked Nov 21 '18 at 12:42
JoeJoe
1
I ran an issue when trying to match a request to api.intercom.com.
api.intercom.io consistently gets changed to api.inter(class) when set as a variable and used in the UrlFetchApp call but it displays as api.intercom.io in the Logger.log output.
Screenshots:
Is there a way to stop this from happening?
javascript google-apps-script urlfetch intercom
javascript google-apps-script urlfetch intercom
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
asked Nov 21 '18 at 12:42
JoeJoe
1
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
asked Nov 21 '18 at 12:42
JoeJoe
1
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
edited Nov 21 '18 at 13:06
Sateesh
2,1471920
2,1471920
asked Nov 21 '18 at 12:42
JoeJoe
1
asked Nov 21 '18 at 12:42
JoeJoe
1
asked Nov 21 '18 at 12:42
JoeJoe
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It only looks "as if" com.io is changed to (class). The error is just visual and has nothing to do with why Urlfetch is NOT working. Use Stackdriver logging: console.log() for accurate representation of the string.
Related Questions:
Intercom- Http status 406
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
I can confirm that it shows up as expected in the logs. However, the error received when trying to executeUrlFetchApp.fetchisInvalid argument: https://api.inter<?>which leads me to believe it isn't just a visual thing. Pretty strange no?
– Joe
Nov 29 '18 at 14:43
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
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%2f53412288%2fhow-to-stop-urlfetchapp-from-turning-com-substring-into-class%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
It only looks "as if" com.io is changed to (class). The error is just visual and has nothing to do with why Urlfetch is NOT working. Use Stackdriver logging: console.log() for accurate representation of the string.
Related Questions:
Intercom- Http status 406
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
I can confirm that it shows up as expected in the logs. However, the error received when trying to executeUrlFetchApp.fetchisInvalid argument: https://api.inter<?>which leads me to believe it isn't just a visual thing. Pretty strange no?
– Joe
Nov 29 '18 at 14:43
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
add a comment |
It only looks "as if" com.io is changed to (class). The error is just visual and has nothing to do with why Urlfetch is NOT working. Use Stackdriver logging: console.log() for accurate representation of the string.
Related Questions:
Intercom- Http status 406
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
I can confirm that it shows up as expected in the logs. However, the error received when trying to executeUrlFetchApp.fetchisInvalid argument: https://api.inter<?>which leads me to believe it isn't just a visual thing. Pretty strange no?
– Joe
Nov 29 '18 at 14:43
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
add a comment |
It only looks "as if" com.io is changed to (class). The error is just visual and has nothing to do with why Urlfetch is NOT working. Use Stackdriver logging: console.log() for accurate representation of the string.
Related Questions:
Intercom- Http status 406
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
It only looks "as if" com.io is changed to (class). The error is just visual and has nothing to do with why Urlfetch is NOT working. Use Stackdriver logging: console.log() for accurate representation of the string.
Related Questions:
Intercom- Http status 406
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
answered Nov 21 '18 at 14:54
TheMasterTheMaster
10.5k3936
10.5k3936
I can confirm that it shows up as expected in the logs. However, the error received when trying to executeUrlFetchApp.fetchisInvalid argument: https://api.inter<?>which leads me to believe it isn't just a visual thing. Pretty strange no?
– Joe
Nov 29 '18 at 14:43
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
add a comment |
I can confirm that it shows up as expected in the logs. However, the error received when trying to executeUrlFetchApp.fetchisInvalid argument: https://api.inter<?>which leads me to believe it isn't just a visual thing. Pretty strange no?
– Joe
Nov 29 '18 at 14:43
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
I can confirm that it shows up as expected in the logs. However, the error received when trying to execute
UrlFetchApp.fetch is Invalid argument: https://api.inter<?> which leads me to believe it isn't just a visual thing. Pretty strange no?– Joe
Nov 29 '18 at 14:43
I can confirm that it shows up as expected in the logs. However, the error received when trying to execute
UrlFetchApp.fetch is Invalid argument: https://api.inter<?> which leads me to believe it isn't just a visual thing. Pretty strange no?– Joe
Nov 29 '18 at 14:43
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
@Joe I believe it's still visual. I also think that the error is 406.
– TheMaster
Nov 29 '18 at 15:17
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%2f53412288%2fhow-to-stop-urlfetchapp-from-turning-com-substring-into-class%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
