Re: Programmatic construction of httprequest?

From: Bill Cohagan (bill_at_teraXNOSPAMXquest.com)
Date: 08/16/04 

Date: Mon, 16 Aug 2004 10:33:46 -0500

Joerg
  Yes, I added the code to explicitly enable the proxy, but still no Fiddler
entries at all. Spike1.aspx is intended to take the data from the form and
stuff it into a database, but of course I could substitute a do nothing
page. I haven't done so because it appears that we're never getting to the
page in the first place. I suppose it's possible that the page is the source
of the error, but that implies:

1.) My breakpoint on the page load handler isn't working.
2.) Fidler isn't catching the request.

  I suppose that it wouldn't hurt to try however. I'll let you know what
happens. Let me know if you think of any other ideas on trouble shooting
this. Also, if you have the time I'd appreciate it if you'd try out your
code on your machine just as a sanity check.

Thanks again for the help.

Bill

"Joerg Jooss" <joerg.jooss@gmx.net> wrote in message
news:Ob563K6gEHA.704@TK2MSFTNGP09.phx.gbl...
> Bill Cohagan wrote:
> > I'm not sure if it passes throught the "pipeline", but it doesn't
> > get far enough to show up in Fiddler.
>
> Oops. So that means this setup
>
> ClientApp --> Fiddler --> WebApp
>
> produces no output in Fiddler? Did you change the code so it uses the
proxy?
>
>
> > The spike1.aspx page itself
> > seems to work OK if I access it via the browser; i.e., I actually
> > submit a form. Also, if I set a breakpoint in the page load event
> > handler for spike1 it never fires. So my guess is that the error
> > occurs before my asp page gets loaded. At one point I found a
> > property that indicated it was a protocol error, but I don't seem to
> > be able to find that now (when the program breaks on the error.)
> > Since it appears not to make it to the asp page I don't really know
> > how to debug this.
> >
> > I've checked the logs, but don't find anything useful there either.
> > Also, I've tried this on a couple of machines and get the same error
> > -- so if it's a config problem it's common to both installations.
>
> What's this spike.aspx doing anyway? Can you substitute it for testing
> purposes with a another page -- assuming it is not a test page already?
>
> Cheers,
>
> --
> Joerg Jooss
> joerg.jooss@gmx.net
>

Relevant Pages