Image Preview and 302 errors

Okay, I think I'm getting to the bottom of the "weirdness" I am experiencing with previewing a DCR (via a PT).

I took a look through the access.log (for apache) and saw these lines:


10.107.65.101 - - [17/Oct/2006:11:43:54 -0400] "GET /iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_1_innerNav_right_on.gif HTTP/1.1" 302 397 0 dpalmer
10.107.65.101 - - [17/Oct/2006:11:43:54 -0400] "GET /iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_1_bullet.gif HTTP/1.1" 302 386 0 dpalmer
10.107.65.101 - - [17/Oct/2006:11:43:54 -0400] "GET /iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_1_dot_whitebg_btm.gif HTTP/1.1" 302 395 0 dpalmer
10.107.65.101 - - [17/Oct/2006:11:43:54 -0400] "GET /iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_1_dot_whitebg_top_3_2.gif HTTP/1.1" 302 399 0 dpalmer

Above are a few of the 302 redirect requests the web server dealt with, but then there are a whole slew of 502 errors. Below is a snippet from our server log:


10.107.65.101 - - [17/Oct/2006:14:22:48 -0400] "GET /iw-cc/iwproxy/iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_0_InnerNav_left_on.gif HTTP/1.1" 502 233 1 dpalmer

10.107.65.101 - - [17/Oct/2006:14:30:14 -0400] "GET /assets/images/InnerNav_left.gif HTTP/1.1" 502 230 0 dpalmer

I've (obviously) confirmed that those images exist, they do, and in the correct location.

Also, the behavior is random, some of the images will be found and served, but if you reload the page, they'll go 502 again.

BTW, I'm very appreciative of those who have been helping. Thank you very much.

Find more posts tagged with

Comments

Adam Stoller

I think you're going to have to play around with running iwproxy in debug-mode.

This log message[indent]10.107.65.101 - - [17/Oct/2006:14:22:48 -0400] "GET /iw-cc/iwproxy/iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_0_InnerNav_left_on.gif HTTP/1.1" 502 233 1 dpalmer[/indent]specifically makes me think that something in your proxy configuration or somewhere(?) is causing the context (I think it's the PATHTRACK cookie or something like that) to get confused and thus the URIs being supplied to the browser don't work.

Since it seems to work sometimes and not others - it's probably a race-condition (e.g.: whether this gets processed before that kind of thing).

Perhaps someone with more experience in this specific area (I consider it a bit of a black-art) can suggest tips for debugging/fixing it further - but I think you're going to have to start with running iwproxy in debug mode.

blinder

I think you're going to have to play around with running iwproxy in debug-mode.

This log message[indent]10.107.65.101 - - [17/Oct/2006:14:22:48 -0400] "GET /iw-cc/iwproxy/iw-mount/default/main/H1/WORKAREA/Development/assets/images/zz_tst_dpalmer_0_InnerNav_left_on.gif HTTP/1.1" 502 233 1 dpalmer[/indent]specifically makes me think that something in your proxy configuration or somewhere(?) is causing the context (I think it's the PATHTRACK cookie or something like that) to get confused and thus the URIs being supplied to the browser don't work.

Since it seems to work sometimes and not others - it's probably a race-condition (e.g.: whether this gets processed before that kind of thing).

Perhaps someone with more experience in this specific area (I consider it a bit of a black-art) can suggest tips for debugging/fixing it further - but I think you're going to have to start with running iwproxy in debug mode.

We have some proxy preconnect settings for livesite and that's really it. I submitted a support ticket, and the first response i got back was that the server is under heavy load.

um, its a development server, and i'm the *only* one doing development on it, so I'm thinking your approach is probably the correct one.

I'll try removing any proxy preconnect settings and see if that improves things.

Thank you for the response Smiley Happy