|
|
|
date: Wed, 25 Jun 2008 00:53:01 -0700 (PDT),
group: microsoft.public.inetsdk.programming.webbrowser_ctl
back
AdditionalHeaders truncated in PassThru APP
Igor
When using your PassThru APP example the *pszAdditionalHeaders value
is occasionally being truncated in the
CTestSink::BeginningTransaction( ..) method
After the code on line 24 HRESULT hr = spHttpNegotiate ?
spHttpNegotiate->BeginningTransaction(szURL, szHeaders,dwReserved,
pszAdditionalHeaders) : S_OK;
The first line of the value of pszAdditionalHeaders is sometimes
truncated, so for example the value is:
Referer:
http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.SMH.NEWS/CTYPE=INDEX/AAMSZ=620X45/PAGEID=719881/ACC_RANDOM=832680/CAT=NE
x-flash-version: 9,0,47,0
When it should be :
Referer:
http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.SMH.NEWS/CTYPE=INDEX/AAMSZ=620X45/PAGEID=719881/ACC_RANDOM=832680/CAT=NEWS/DOMAIN=SMH.COM.AU/SITE=SMH/ISIFRAME=YES/POS=1
x-flash-version: 9,0,47,0
Are you able to tell me where/how I could correct the problem ?
thanks
Peter
date: Wed, 25 Jun 2008 00:53:01 -0700 (PDT)
author: peter.boot
Re: AdditionalHeaders truncated in PassThru APP
On Jun 25, 5:53 pm, "peter.boot" wrote:
> Igor
>
> When using your PassThru APP example the *pszAdditionalHeaders value
> is occasionally being truncated in the
> CTestSink::BeginningTransaction( ..) method
>
> After the code on line 24 HRESULT hr = spHttpNegotiate ?
> spHttpNegotiate->BeginningTransaction(szURL, szHeaders,dwReserved,
> pszAdditionalHeaders) : S_OK;
>
> The first line of the value of pszAdditionalHeaders is sometimes
> truncated, so for example the value is:
> Referer:http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
> x-flash-version: 9,0,47,0
>
> When it should be :
> Referer:http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
> x-flash-version: 9,0,47,0
>
> Are you able to tell me where/how I could correct the problem ?
>
> thanks
>
> Peter
Threre is a pattern to it, the Referer header for swf files get
trancated at around 140 to 143 characters. You can see it for yourself
on cnn.com or smh.com.au
date: Wed, 25 Jun 2008 02:21:05 -0700 (PDT)
author: peter.boot
Re: AdditionalHeaders truncated in PassThru APP
On Jun 25, 7:21 pm, "peter.boot" wrote:
> On Jun 25, 5:53 pm, "peter.boot" wrote:
>
>
>
> > Igor
>
> > When using your PassThru APP example the *pszAdditionalHeaders value
> > is occasionally being truncated in the
> > CTestSink::BeginningTransaction( ..) method
>
> > After the code on line 24 HRESULT hr = spHttpNegotiate ?
> > spHttpNegotiate->BeginningTransaction(szURL, szHeaders,dwReserved,
> > pszAdditionalHeaders) : S_OK;
>
> > The first line of the value of pszAdditionalHeaders is sometimes
> > truncated, so for example the value is:
> > Referer:http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
> > x-flash-version: 9,0,47,0
>
> > When it should be :
> > Referer:http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
> > x-flash-version: 9,0,47,0
>
> > Are you able to tell me where/how I could correct the problem ?
>
> > thanks
>
> > Peter
>
> Threre is a pattern to it, the Referer header for swf files get
> trancated at around 140 to 143 characters. You can see it for yourself
> on cnn.com or smh.com.au
sorry that should be truncated at around 140 to 143 characters
date: Wed, 25 Jun 2008 02:28:43 -0700 (PDT)
author: peter.boot
Re: AdditionalHeaders truncated in PassThru APP
"peter.boot" wrote in message
news:19b0aeab-ba3e-49a3-9a87-563a12f552ff@v26g2000prm.googlegroups.com
> When using your PassThru APP example the *pszAdditionalHeaders value
> is occasionally being truncated in the
> CTestSink::BeginningTransaction( ..) method
>
> After the code on line 24 HRESULT hr = spHttpNegotiate ?
> spHttpNegotiate->BeginningTransaction(szURL, szHeaders,dwReserved,
> pszAdditionalHeaders) : S_OK;
>
> The first line of the value of pszAdditionalHeaders is sometimes
> truncated, so for example the value is:
> Referer:
> http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.SMH.NEWS/CTYPE=INDEX/AAMSZ=620X45/PAGEID=719881/ACC_RANDOM=832680/CAT=NE
> x-flash-version: 9,0,47,0
>
> When it should be :
> Referer:
> http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.SMH.NEWS/CTYPE=INDEX/AAMSZ=620X45/PAGEID=719881/ACC_RANDOM=832680/CAT=NEWS/DOMAIN=SMH.COM.AU/SITE=SMH/ISIFRAME=YES/POS=1
> x-flash-version: 9,0,47,0
>
> Are you able to tell me where/how I could correct the problem ?
You get the correct headers. I checked with a packet sniffer (Ethereal),
and in fact the request is sent with this truncated Referer header. I'm
not sure why this happens, but you are getting the same thing the server
will be getting.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
date: Wed, 25 Jun 2008 08:07:32 -0400
author: Igor Tandetnik
Re: AdditionalHeaders truncated in PassThru APP
On Jun 25, 10:07 pm, "Igor Tandetnik" wrote:
> "peter.boot" wrote in message
>
> news:19b0aeab-ba3e-49a3-9a87-563a12f552ff@v26g2000prm.googlegroups.com
>
>
>
> > When using your PassThru APP example the *pszAdditionalHeaders value
> > is occasionally being truncated in the
> > CTestSink::BeginningTransaction( ..) method
>
> > After the code on line 24 HRESULT hr = spHttpNegotiate ?
> > spHttpNegotiate->BeginningTransaction(szURL, szHeaders,dwReserved,
> > pszAdditionalHeaders) : S_OK;
>
> > The first line of the value of pszAdditionalHeaders is sometimes
> > truncated, so for example the value is:
> > Referer:
> >http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
> > x-flash-version: 9,0,47,0
>
> > When it should be :
> > Referer:
> >http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
> > x-flash-version: 9,0,47,0
>
> > Are you able to tell me where/how I could correct the problem ?
>
> You get the correct headers. I checked with a packet sniffer (Ethereal),
> and in fact the request is sent with this truncated Referer header. I'm
> not sure why this happens, but you are getting the same thing the server
> will be getting.
> --
> With best wishes,
> Igor Tandetnik
>
> With sufficient thrust, pigs fly just fine. However, this is not
> necessarily a good idea. It is hard to be sure where they are going to
> land, and it could be dangerous sitting under them as they fly
> overhead. -- RFC 1925
So just to clarify the what you are saying the truncated Referer
header what is being sent to the browser and so that is what is seen
by CTestSink::BeginningTransaction ? In other words this can't be
fixed ?
date: Wed, 25 Jun 2008 05:21:57 -0700 (PDT)
author: peter.boot
Re: AdditionalHeaders truncated in PassThru APP
"peter.boot" wrote in message
news:10ba9a16-324d-446f-89e9-b7a884c7918f@a32g2000prf.googlegroups.com
> On Jun 25, 10:07 pm, "Igor Tandetnik" wrote:
>> "peter.boot" wrote in message
>> news:19b0aeab-ba3e-49a3-9a87-563a12f552ff@v26g2000prm.googlegroups.com
>>> The first line of the value of pszAdditionalHeaders is sometimes
>>> truncated, so for example the value is:
>>> Referer:
>>> http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
>>> x-flash-version: 9,0,47,0
>>
>>> When it should be :
>>> Referer:
>>> http://direct.fairfax.com.au/hserver/SITE=ONL.MH.SMH.NEWS/AREA=NEWS.S...
>>> x-flash-version: 9,0,47,0
>>
>>> Are you able to tell me where/how I could correct the problem ?
>>
>> You get the correct headers. I checked with a packet sniffer
>> (Ethereal), and in fact the request is sent with this truncated
>> Referer header. I'm not sure why this happens, but you are getting
>> the same thing the server will be getting.
>
> So just to clarify the what you are saying the truncated Referer
> header what is being sent to the browser
It is being sent by the browser to the server.
> and so that is what is seen
> by CTestSink::BeginningTransaction ? In other words this can't be
> fixed ?
As far as the APP is concerned, it ain't broken in the first place. You
see the header exactly as the browser wants it sent to the server in an
HTTP request.
I don't know why the browser wants to send a truncated header, nor how
its decision could be influenced, if at all.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
date: Wed, 25 Jun 2008 08:56:24 -0400
author: Igor Tandetnik
|
|
