× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Brad,

After some research I found that HTTPAPI allows you to add an exit point procedure to add header values. I am right in the middle of testing it but I am sure that it will do what I need.

Thanks,

Scott


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Bradley Stone
Sent: Thursday, October 24, 2013 1:23 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Provide referer when accessing web service with HTTPAPI

What we did with GETURI to solve issues like this is allow the user to use up to 10 user defined headers and values. This lets them add things like referrer, or other special headers that may be required (like SOAP-Action, etc).

Brad
www.bvstools.com


On Thu, Oct 24, 2013 at 1:55 PM, Scott Mildenberger < SMildenberger@xxxxxxxxxxxxxxxxxx> wrote:

HTTPAPI does allow certain fields in the header to be defined but
referer is not one of them. I guess I can just modify it to add
referer when it builds the header, it currently doesn't specify it at
all so I will just add it.

Thanks,

Scott


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Kevin Turner
Sent: Thursday, October 24, 2013 12:45 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Provide referer when accessing web service with
HTTPAPI

What is preventing you from providing the referer (sic) in the HTTP
header to placate the web service?

I would imagine HTTPAPI allows you to define the HTTP header for your
request doesn't it?

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Scott Mildenberger
Sent: 24 October 2013 17:05
To: web400@xxxxxxxxxxxx
Subject: [WEB400] Provide referer when accessing web service with
HTTPAPI

I am accessing a web service using HTTPAPI procedure http_url_get_raw().
Since the access is not coming from a web page it is being rejected
because the referer is blank. The web service does have an option to
'Enable Blank Referers' which will allow it to work but they warn that
this may allow others to access the web service under our account. If
this is not enabled I cannot access even by putting the address into
the browser, it must be embedded as a link in a web page to work.

Is there a way to provide the referer? Is setting up my account to
allow blank referers much of an issue as all of my access to this
account is from behind our firewall?

Thanks,

Scott Mildenberger
Programmer/Analyst
Davis Transport Inc.
Missoula, MT
406-728-5510 x128
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.