UrlFetchApp failing (unexpected error) when URL contains HTTP Basic Authentication credentials [36758922]

In Progress

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jun 5, 2013 08:38AM

----------------------------------------------
What steps will reproduce the problem?
----------------------------------------------
Use UrlFetchApp.fetch to perform an HTTP Basic Authentication Request with the credentials inserted in the URL (e.g.

https://foo:bar@example.org)

----------------------------------------------
What is the expected output?
----------------------------------------------
The request should be fired

----------------------------------------------
What do you see instead?
----------------------------------------------
Instead UrlFetchApp throws the following error:

Unexpected error:

https://foo:bar@example.org

----------------------------------------------
Sample Code
----------------------------------------------
See

http://stackoverflow.com/questions/16773678/unexpected-error-on-urlfetchapp-fetch-in-google-apps-script

----------------------------------------------
Project Key
----------------------------------------------
We do not want to share as the issue is easily reproducible and our project contains private data (Keys to external APIs)

----------------------------------------------
On which browser & OS?
----------------------------------------------
Any

Comments

gk...@google.com <gk...@google.com> #2Jun 5, 2013 02:01PM

Assigned to gk...@google.com.

Thanks for your report. We have a bug open to address this issue.

[Deleted User] <[Deleted User]> #3Jun 10, 2013 10:13AM

Thanks. Any ETA for a fix at this point / What would be a reasonable estimate?

sl...@google.com <sl...@google.com> #4Jun 19, 2013 06:36PM

An alternative is to use the HTTP headers for basic authentication:

http://productforums.google.com/forum/#!topic/apps-script/oDsa9L6R87Q

jp...@gmail.com <jp...@gmail.com> #5Jul 4, 2013 01:48AM

the url to

productforums.google.com is ok ? I get "There is no group named “apps-script”."

gk...@google.com <gk...@google.com> #6Jul 9, 2013 02:36PM

An example of the alternative method slieberman mentioned is below. Note that you will need to use a valid URL instead of the example URL shown below.

function test() {
Logger.log('Basic Auth in URL');
try {
var response = UrlFetchApp.fetch('

http://user1:user1@test.example.com', {
muteHttpExceptions: true
});
Logger.log('Response Code: ' + response.getResponseCode());
} catch(e) {
Logger.log('Failure: ' + e);
}

Logger.log('Basic Auth in header');
var response = UrlFetchApp.fetch('

http://test.example.com', {
headers: {
'Authorization': 'Basic ' + Utilities.base64Encode('user1:user1')
},
muteHttpExceptions: true
});
Logger.log('Response Code: ' + response.getResponseCode());
}

[Deleted User] <[Deleted User]> #7Sep 27, 2013 11:04PM

Hi,

I wonder, any progress in this matter.
I encounter the same problem using UrlFetchApp

Regards

ab...@gmail.com <ab...@gmail.com> #8May 7, 2014 06:06PM

Hi I had a similar problem that occured randomly after a number of times the app was executed.

The Error was : Unexpected Error.

I found one reason that this might happen. In my code the GET call was adding on a filter array of parameters. As i did not initialize the array , the parametre was getting added and I assume that the length exceed some set limit and crashed.
Hopefully a check and error message can be given to warn other developers of this type of errors.

pa...@gmail.com <pa...@gmail.com> #9Sep 21, 2014 12:02PM

I have an API which appears to have poorly executed http authentication that won't process correctly via the header, and will only accept it in the URL. Progress on this bug would be very helpful.

33...@gmail.com <33...@gmail.com> #10Jan 3, 2015 07:42AM

I also encountered the same problems.

ry...@google.com <ry...@google.com> #11Apr 8, 2016 08:01PM

Reassigned to ap...@google.com.

Unassigning

ry...@google.com <ry...@google.com> Apr 24, 2017 09:26PM

Accepted by ap...@google.com.

ma...@gmail.com <ma...@gmail.com> #12May 20, 2020 10:23AM

Any progress on this? I cannot use the basic headers as an alternative

ss...@gmail.com <ss...@gmail.com> #13Sep 18, 2020 12:09PM

I am sending Credentials (Bearer token) in header only and still getting this error many times. (But not all the time).
We have apps published in G-suite marketplace and I am seeing lot of error logs with this error.