UrlFetchApp: Option to turn off automatic redirects in the fetch method. [36752903]

Fixed

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Oct 21, 2010 10:21AM

Request Summary:

UrlFetchApp.fetch automatically follows redirects, but does not handle cookies upon redirection.
This makes it impossible to access services where consecutive requests rely on session cookies.

Adding followRedirects=false option will allow to manually handle both redirects and cookies.

Notes:

The requested feature is already present in the App Engine API for URLFetch -

http://code.google.com/appengine/docs/python/urlfetch/fetchfunction.html.

Comments

ma...@gmail.com <ma...@gmail.com> #3Aug 22, 2012 11:03PM

Also having the option to either pan or zoom with the scroll wheel would be useful.

pr...@gmail.com <pr...@gmail.com> #4Oct 4, 2012 11:32AM

"Add the ability to scroll using the mouse wheel, add it to default UI, and
let developers disable it."

that way will help user for zoom in & zoom out easier..

ia...@gmail.com <ia...@gmail.com> #5Oct 15, 2012 03:49PM

I need mouse wheel to operate zooming in and out.
I have wait for several weeks already.
develop from Beijing China

fa...@gmail.com <fa...@gmail.com> #6Oct 16, 2012 04:02AM

Mousewheel zooming please! :)

mi...@gmail.com <mi...@gmail.com> #7Nov 20, 2012 07:15PM

I can see that this issue is "Acknowledged", but is there any way to see when it
will be released?

t....@gmail.com <t....@gmail.com> #8Dec 29, 2012 05:37AM

When an issue in this tracker changes status (like from Acknowledged->Fixed), you'll
receive an email saying so. We generally don't reveal timelines for feature requests.

ko...@gmail.com <ko...@gmail.com> #9Jan 24, 2013 08:53PM

Marked as fixed.

Pamela, for being fair: this is not feature request. This is backward compatibility
issue.
I think this is the only one blocking issue for migrating from GMap API v2 to v3.

ad...@gmail.com <ad...@gmail.com> #10Jan 24, 2013 09:07PM

#9, this is definitely not the only feature missing in v3. The overview page states
"The initial launch has a smaller feature set than that available in the V2 API."

is...@layer0.llnw.com <is...@layer0.llnw.com> #11Jan 24, 2013 09:09PM

#8 I appreciate the quick answer, right now I'm about to choose to either develop a
new site on the old v2 or the new v3 api, the site is scheduled to be in production
within this year, what are the pros and cones i have to consider?

ia...@gmail.com <ia...@gmail.com> #12Jan 25, 2013 04:49AM

I'd recommend going with v2 API for now. It is the safer choice. I recently strated a
project with v3 and had to port back to v2 in a hurry because I ran into compatibility
issues with IE.

al...@gmail.com <al...@gmail.com> #13Jan 25, 2013 08:27AM

pleeeeaaaaassseeeeeeeee!!! ;)

tc...@blue-efficience.com <tc...@blue-efficience.com> #14Jan 25, 2013 08:37AM

Is it ready yet? This is a great feature you must include it!

pr...@gmail.com <pr...@gmail.com> #15Jan 26, 2013 02:07AM

Nianwei created an open-source scroll wheel zoom implementation, you may want to try it
out:

http://groups.google.com/group/google-maps-utility-library-
v3/browse_thread/thread/f421e075eb63d2ba

lu...@gmail.com <lu...@gmail.com> #16Jan 28, 2013 02:05AM

Really want to see this feature added onto V3 asap please....