DownloadFile, InternetGet, InternetPush, API and an Auth Token
Quote from PaulJonestindall on April 12, 2024, 2:32 pmI have an internet API problem.
Currently I'm using an API to retrieve an XML file using the DownloadFile action command. My source is now changing this to include an Auth-Token.
I am unfamiliar with how this works really.For example, my current code is this:
DownloadFile “http://task.myweburl.loc/task/api/mark_occurrences/?site=[site]&tag_id=[pournumber]&format=xml” "[PubDir]markocc.xml" "HideProgress+Async"
and this gives me an XML file.
The API has now changed to:
https://task.myweburl.io/task/api/mark_occurrences/?site=[site]&tag_id=[pournumber]&format=xmland will now require an Auth-Token. I've received this information that I don't know how to handle.
Headers (6)
Accept: */*
Accept-encoding: gzip, deflate
Authorization: Token token_value
Connection: keep-alive
Host: localhost:8000
User-agent: python-requests/2.28.2Would InternetGet or Push be of use?
Help and Suggestions please!
I have an internet API problem.
Currently I'm using an API to retrieve an XML file using the DownloadFile action command. My source is now changing this to include an Auth-Token.
I am unfamiliar with how this works really.
For example, my current code is this:
DownloadFile “http://task.myweburl.loc/task/api/mark_occurrences/?site=[site]&tag_id=[pournumber]&format=xml” "[PubDir]markocc.xml" "HideProgress+Async"
and this gives me an XML file.
The API has now changed to:
https://task.myweburl.io/task/api/mark_occurrences/?site=%5Bsite%5D&tag_id=%5Bpournumber%5D&format=xml
and will now require an Auth-Token. I've received this information that I don't know how to handle.
Headers (6)
Accept: */*
Accept-encoding: gzip, deflate
Authorization: Token token_value
Connection: keep-alive
Host: localhost:8000
User-agent: python-requests/2.28.2
Would InternetGet or Push be of use?
Help and Suggestions please!
Quote from luishp on April 12, 2024, 8:59 pm@pauljonestindall I'm afraid VisualNEO Win is not prepared to get online files using HTTP headers.
It's not possible to include HTTP headers directly within a URL. HTTP headers are part of the HTTP request and response structure, used to pass additional information between the client and server, which is separate from the URL itself.
A URL is used to identify the location of a resource on the internet and can include components such as the protocol, domain, path, and query parameters. However, HTTP headers, which can include information such as content type, cookies, user-agent, and more, are transmitted in the HTTP request or response headers, not in the URL.
If you need to convey information that might typically be in a header, but must use a URL to do so, you can sometimes use query parameters or path parameters to pass this information in a modified form. However, this is not a substitute for using HTTP headers where they are required for controlling the behavior of HTTP requests and responses.
VisualNEO Web is prepared for this kind of information exchange.
Sorry.
@pauljonestindall I'm afraid VisualNEO Win is not prepared to get online files using HTTP headers.
It's not possible to include HTTP headers directly within a URL. HTTP headers are part of the HTTP request and response structure, used to pass additional information between the client and server, which is separate from the URL itself.
A URL is used to identify the location of a resource on the internet and can include components such as the protocol, domain, path, and query parameters. However, HTTP headers, which can include information such as content type, cookies, user-agent, and more, are transmitted in the HTTP request or response headers, not in the URL.
If you need to convey information that might typically be in a header, but must use a URL to do so, you can sometimes use query parameters or path parameters to pass this information in a modified form. However, this is not a substitute for using HTTP headers where they are required for controlling the behavior of HTTP requests and responses.
VisualNEO Web is prepared for this kind of information exchange.
Sorry.