| ASP URL Question for Discoverer Portlet Hyperlink [message #322464] |
Fri, 23 May 2008 11:32  |
eguether
Messages: 3
Registered: May 2008
Location: New Jersey, USA
|
Junior Member |
|
|
This may seem like an unusual question for this forum, but I thought I'd ask anyway. It's for a dynamic hyperlink that we use in Discoverer and Portal to provide a one-click URL to users to open a shipping webpage via the Internet for an Oracle shipment record whose tracking number (airway bill #) is stored in EBS 11i. This dynamic tracking link works well for us today in EBS 11i and Portal 10gR2 for shipments via FedEx, UPS, and DHL as noted in my OAUG COL'06 white paper. But I'm having an issue with BAX Global due to the ASP functionality of their tracking website.
Here's the issue: We have a BAX Global shipment in our Oracle 11i system with a tracking number 'BKK00086205' stored in the airway bill column. I can use that tracking number on BAX's website to track the shipment; the tracking number is including in the dynamic URL:
http://www.baxglobal.com/defaultFrm.asp?pg=%2FTracking%2F&s=ShipmentTracking&trackby=H&trackbyno=BKK00086205&x=4& y=12
If I paste this URL into a new browser session (IE or Firefox), the website automatically gets diverted to the shipping carrier's US home ASP page:
http://www.baxglobal.com/US.asp/
But if I then paste in the dynamic URL with tracking number again from the US ASP home page, the browser successfully goes to the tracking page for that shipment.
Does anyone know how I can modify a dynamic URL to skip the initial step of diverting to the ASP website's homepage?
Best regards,
Eric
___________________________
|
|
|
|
| Re: ASP URL Question for Discoverer Portlet Hyperlink [message #322485 is a reply to message #322464] |
Fri, 23 May 2008 13:12  |
kmmfoo
Messages: 38
Registered: June 2005
Location: massachusetts
|
Member |
|
|
I would bet that it's something BAX is doing on their end. For example, perhaps they are checking the "referrer", or perhaps for the existence of a cookie, and if it's not an expected value they send browsers to that "start" page.
Okay, I tested it, and it seems like it's the second option: cookies. I'd never been to their site before, and when I went there they created 4 session cookies and 3 persistent cookies on my PC. When I remove the 4 session cookies, it sends me to the default "start" page; but once those cookies exist you seem to be okay, browsers go direct to the tracking page.
So here's an inefficient hack workaround: Create an invisible iframe inside your page, and before you send the users to BAX, try to load the tracking page inside that iframe. Once that invisible copy of the page has loaded, then open BAX in another window. I'd bet it works fine.
HTH.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
