Loosing Set-Cookie attributes in Http Header response [36753169]

Fixed

Bug

Status Update

No update yet.

Description

tc...@gmail.com

created issue #1

Apr 26, 2011 08:25PM

What steps will reproduce the problem?
1. Do a "var Response = UrlFetchApp.fetch(sURL);" to a website which ask the setting of more than one Cookie on your computer (multiple Set-Cookie attribute in header)
2. Extract the header doing "var oHeader = Response.getHeaders();"
3. Prompt the header and you will see a "Set-Cookie" attribute with the value of only one of the Cookie the website sent. (actually it is the last cookie appearing in the header which seems to overwrite the first ones)

I guess the value behind "Set-Cookie" attribute should be a string array but it is a single string.

In my case the first cookie in 4 sent by the website I fetch is the one I need. But I get only the 4th in 4.

Am I missing something ?

Thierry

Comments

jo...@bhsupplies.com.au <jo...@bhsupplies.com.au> #2May 27, 2011 03:43AM

Disabling all extensions does not fix the problem.

ev...@google.com <ev...@google.com> #4Jun 9, 2011 03:47PM

Adding debug log.

tc...@gmail.com <tc...@gmail.com> #5Jun 17, 2011 04:07PM

Do you have crash reporting enabled? If so, a crash id should be dumped, and if you give that to us, then we can look up what caused the crash.

tc...@gmail.com <tc...@gmail.com> #6Sep 13, 2011 11:01AM

My client_id appears to be B7776A6E-F752-1E5B-E46B-ACD5F961EE30.

I see crash_count: 0, but since I've enabled it I've gotten it to crash twice.

Seems to happen immediately after geolocation is finished.

tc...@gmail.com <tc...@gmail.com> #7Dec 16, 2011 03:56PM

I only see 2 browser crashes from your client id:

Stack trace:

Thread 0 *CRASHED* ( SIGSEGV @ 0x00000020 )
0xb6c306ca [libdbus-glib-1.so.2.1.0 + 0x0000d6ca]
0xb6c30be4 [libdbus-glib-1.so.2.1.0 + 0x0000dbe4]
0xb6c324f9 [libdbus-glib-1.so.2.1.0 + 0x0000f4f9]
0xb6c2f17e [libdbus-glib-1.so.2.1.0 + 0x0000c17e]
0xb6c07790 [libdbus-1.so.3.4.0 + 0x0001d790]
0xb6bf73c5 [libdbus-1.so.3.4.0 + 0x0000d3c5]
0xb6bf9991 [libdbus-1.so.3.4.0 + 0x0000f991]
0xb6c2a92c [libdbus-glib-1.so.2.1.0 + 0x0000792c]
0xb705b5e4 [libglib-2.0.so.0.2400.1 + 0x0003b5e4]
0xb705f2d7 [libglib-2.0.so.0.2400.1 + 0x0003f2d7]
0xb705f4b7 [libglib-2.0.so.0.2400.1 + 0x0003f4b7]
0x08707d34 [chrome - base/message_pump_glib.cc:195] base::MessagePumpForUI::RunWithDispatcher(base::MessagePump::Delegate*, base::MessagePumpForUI::Dispatcher*)
0x0870796f [chrome - ./base/message_pump_glib.h:59] base::MessagePumpForUI::Run(base::MessagePump::Delegate*)
0x086e00f3 [chrome - base/message_loop.cc:214] MessageLoop::RunInternal()
0x086e0161 [chrome - base/message_loop.cc:617] MessageLoopForUI::Run(base::MessagePumpForUI::Dispatcher*)
0x08073625 [chrome - chrome/browser/browser_main.cc:198] BrowserMain(MainFunctionParams const&)
0x0806cb4a [chrome - chrome/app/chrome_dll_main.cc:861] ChromeMain
0x0806cf5f [chrome - chrome/app/chrome_exe_main_gtk.cc:50]

as...@google.com <as...@google.com> #8Dec 16, 2011 05:11PM

Assigned to as...@google.com.

Are they the same? I can reproduce it a few more times if you'd like.

ma...@gmail.com <ma...@gmail.com> #9Apr 16, 2012 08:48PM

I'm guessing geolocation tries to initialize glib-dbus, which is crashing, possibly due to a race condition. Perhaps r50652 fixes this, or cause the crash to happen sooner?

ko...@gmail.com <ko...@gmail.com> #10Oct 30, 2012 06:59PM

Marked as fixed, reassigned to ko...@gmail.com.

[Empty comment from Monorail migration]

ek...@google.com <ek...@google.com> Apr 5, 2017 02:03PM

Reassigned to ek...@google.com.