Hi where are you seeing the invalid cookies(sorry havent seen your screencast). i tried with firefox to login I get
*http://authnet.danielwatrous.com/testjmeter/wp-login.php* Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ Set-Cookie: wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307234422%7Cc8c4e5bb5f9bacc38cf0d3f6a5a19125; path=/testjmeter/wp-content/plugins; httponly Set-Cookie: wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307234422%7Cc8c4e5bb5f9bacc38cf0d3f6a5a19125; path=/testjmeter/wp-admin; httponly Set-Cookie: wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307234422%7C0499d7fe3fd97c79cefda4d96eb98156; path=/testjmeter/; httponly *http://authnet.danielwatrous.com/testjmeter/wp-admin/* Set-Cookie: wp-settings-1=m8%3Dc%26m6%3Dc%26m10%3Dc%26m11%3Do%26m7%3Do%26m4%3Dc%26m12%3Dc%26m0%3Dc%26m1%3Dc; expires=Sat, 02-Jun-2012 00:40:23 GMT; path=/testjmeter/ Set-Cookie: wp-settings-time-1=1307061623; expires=Sat, 02-Jun-2012 00:40:23 GMT; path=/testjmeter/ Atleast the browser behaves correctly - as far as I remember setting the expiry date to the past is equivalent to deleting the cookie - so if you set expiry in the past , then the browser wont send the cookie either regards deepak On Thu, Jun 2, 2011 at 5:30 PM, Daniel Watrous <daniel.watr...@gmail.com>wrote: > Did any of you notice that the Date of the request is accurate and so > are some of the cookies? WordPress seems to deliberately send the > login related cookies with the year old expiration. Others are fine. > > I mention this because there seems to be an idea that the server time > is configured wrong. > > On Thu, Jun 2, 2011 at 4:32 PM, sebb <seb...@gmail.com> wrote: > > On 2 June 2011 17:26, Bruce Ide <flyingrhenqu...@gmail.com> wrote: > >> > I think it's a bit premature to suggest that WordPress is broken. It > >> > is used on tens of millions of sites and people are able to login > fine > >> >every day. > >> > >> Number of users is not a quality metric! Look at Windows... (Heh heh > heh) > >> > >>> Well there's your problem! > >>> > >>> That only affects the cookies that are stored in the cookies file > >>> (which is not normally used). > >>> > >>> > >> Doh! It seemed like such a likely culprit, too! > >> > > > > The actual expiry code is similar: > > > > // Store session cookies as well as unexpired ones > > if (exp == 0 || exp >= System.currentTimeMillis()) { > > newCookie.setVersion(cookie.getVersion()); > > add(newCookie); // Has its own debug log; removes > > matching cookies > > } else { > > removeMatchingCookies(newCookie); > > if (debugEnabled){ > > log.debug("Dropping expired Cookie: > > "+newCookie.toString()); > > } > > } > > > > > >> > >>> > I'd be really hesitant to change the behavior of the test environment > to > >>> > mask a bug you uncovered, though. Sending expired cookies IS a bug, > and > >>> it's > >>> > something the guys running the server should fix. > >>> > >>> If this is a general problem, I suppose it might make sense to add an > >>> option to remove the expiry date from stale cookies, turning them into > >>> session cookies. > >>> But AFAIK this is the first time this has been reported [, and might > >>> cause indigestion (!) in some cases]. > >>> > >>> > >> Well it sounds like the web browser is also storing and using the > expired > >> cookie, and the remote server is honoring it! That's like 3 different > bugs > >> he's uncovered so far! At this point I'd be rampaging like... something > that > >> rampages a LOT... through 2 or 3 different bug forums. > >> > >> I'm sure the Firefox guys would say "No it's not!" At least some people > in > >> the "real world" do check cookie expiry dates, but it's probably > "optional". > >> I'm not inclined to go digging through RFCs to find out. > >> > >> I'd say Wordpress sending out cookies from last year means someone > hasn't > >> been minding a server like they should be. That really IS a problem. > > > > Agreed. > > > >> I suppose you could add a "Remove expiration dates" to the cookie > manager > >> panel, or a "send expired cookies" checkbox to the httpclient. Probably > >> wouldn't be a huge amount of coding, and would probably be only vaguely > >> atrocious. > > > > It's fairly simple to change the code itself, but there is additional > > work needed to implement the GUI change and update the documentation. > > > > It's not yet clear if this is a general problem affecting multiple > > servers, or just WordPress servers, or just an issue with the > > particular WordPress host. > > > >> Or perhaps a sampler or postprocessor that allows you to manipulate > explicit > >> cookie values? That'd be a bit more work, but might be more palatable. > > > > That can be done already with the Regex Processor and Header Manager, > > or using the BSH or BSF test elements. > > > > Might just be simpler to change the time on the box running JMeter ... > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
