Strange thing about url

[peterH]

In a browse I've got an Other button that calls another 'child' browse. It's working here but not at a customer site. In my search for a solution I discovered that the url when calling the second browse is different at the two locations (but this was not really causing the problem).

Here:
http://127.0.0.1:88/webfakturaer?WEBSAGER__websager_id=30

Customer:
http://xxx.xxx.0.12:88/webfakturaer?__Referer__=http%3A//xxx.xxx.0.12%3A88/NyeSagerAcceptForm&WEBSAGER__websager_id=38

Where does the referer stuff come from. And why the difference. Is it perhaps a server setting?

Peter

Update: It does create a problem. I cannot serve pdf-files because the page cannot be found (the url has got the referer stuff in it).

[Bruce]

Hi Peter,

The referer is being added because you are using IE on the client machine, and in some cases IE does not add the referer to Ajax calls. However it's just a parameter, so should not affect the page you are trying to fetch, webfakturaer.

Put some debugging in that procedure to see if it is called.

also test on the client with a different browser to see if that has an effect.

cheers
Bruce

[peterH]

Hi Bruce,

You're absolutely right about the browsers, my fault that I didn't test that 

However, I've got everything working now - but only in FF. In IE my ServeDocument page doesn't work (I'm displaying a pdf).

FF URL: .../ServeDocument?docid=188
IE URL: .../ServeDocument?_Referer_=http%3A//192.168.1.4%3A2019/SagerForm&docid=188

Anything I can do in my code to overcome this?

Thanks
Peter

[Bruce]

Does it fail with IE on your development computer?

Cheers
Bruce

[peterH]

Yep - seems like it chokes on the url. I get "IE cannot display the web page".

Peter

FYI: C6.3 9056 and NT5.09 (yeah, I know, dinosaur and all <g>)