Correct me if I'm wrong but I'm thinking that those URLs do not contain the IP addresses of hosts accessing your proxy, but rather they are outbound POST requests FROM your 'clients' TO remote destinations.
This portion of the 2nd type URL you provided is typical of a 'folder' with a randomly generated name.
Code:
/IVmYwvJKhJFesFjK/
Folders like that are often used for legit purposes but those URLs also resemble a Slow Lorris attack. In that sort of scenario, the path and resource are arbitrary and likely don't exist. The objective is to flood the server with a bunch of requests that won't time-out, because the very end of the request header is crafted so it is purposely missing the full 0d 0a 0d 0a that the server expects.
Not really enough evidence to determine from your post.
EDIT: My first post on this forum and unfortunately, I NECROed. Sorry all.....
Last edited by bashomatic; 03-14-2017 at 06:14 PM..
Reason: Apologized for thread necro.
Hello
one of my sites i host is doing somewhat well in the search engines, and i would like to watch the raw log files while looged in with telenet
is there a way to do this.
thanx
Mike (2 Replies)
Hi,
I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Hi there
I am currently trying to access an http site using the wget utility from a solaris box. I am going through proxies to do this and we have two types of proxies.
For the first one, which is a netcache proxy, I am able to use the wget command to export the proxy information
export... (2 Replies)
How I can get the logs that are getting stored in specific location in unix server
through an Apache web server installed in unix server?
Requirement is to access the logs through the URL in windows browser without any access. (1 Reply)
Hello Team,
I need help to improve my script which is used to grep 500 error messages in the logs.
I am using following logic in the script to grep 500 error messages in the logs.
var1=`awk '$9 == "500"' access_log | tail -1`
The above logic is not useful if logs are not getting... (1 Reply)
I need to configure a proxy on my local machine to use an upstream proxy (installed on another machine). The upstream proxy requires Digest/NTLM authorization. I want the local proxy to deal with the upstream proxy's authorization details and provides authorization free access to users that connect... (0 Replies)
Discussion started by: Russel
0 Replies
LEARN ABOUT DEBIAN
globus_gass_transfer_referral
Referrals(3) globus gass transfer Referrals(3)NAME
Referrals -
Functions
globus_size_t globus_gass_transfer_referral_get_count (globus_gass_transfer_referral_t *referral)
char * globus_gass_transfer_referral_get_url (globus_gass_transfer_referral_t *referral, globus_size_t index)
int globus_gass_transfer_referral_destroy (globus_gass_transfer_referral_t *referral)
Detailed Description
The GASS Transfer API supports referring URL requests to alternate URLs via referrals.
Referrals are essentially pointers to another URL or URLs which contain the same file as the original location which a client has requested
of a server. Referrals may span multiple protocol schemes, though not all protocols may be able to generate referrals. For example, an HTTP
server may refer a client to another HTTP server, an HTTPS server.
Upon receiving a referred response from a server, a client should query the request handle to determine from where the file can be
retrieved.
Function Documentation
globus_size_t globus_gass_transfer_referral_get_count (globus_gass_transfer_referral_t *referral)
Get the number of URLs in this referral. This function examines the referral to determine if the number of URLs which are contained in it.
Each of these URLs should either point to another referral, or to a URL containing the equivalent file as the original URL request which
caused this referral.
Parameters:
referral The referral structure to query.
Returns:
This function returns the number of URL entries in the referral, or 0, if there are none.
char* globus_gass_transfer_referral_get_url (globus_gass_transfer_referral_t *referral, globus_size_tindex)
Get a URL string from a referral. This function examines the referral to retrieve a URL string from it. A valid referal will contain one or
more strings. They are indexed from 0 to the value returned by globus_gass_transfer_referral_get_count() - 1.
The string returned by this function must not be freed by the caller. It will remain valid until the referral structure is destroyed.
Parameters:
referral The referral structure to query.
index The URL to extract from the referral.
Returns:
This function returns a string pointer containing the URL, or NULL if the index or referral were invalid.
int globus_gass_transfer_referral_destroy (globus_gass_transfer_referral_t *referral)
Free all memory used by a referral. This function frees all memory used by this referral. After calling this function, the strings returned
by calling globus_gass_transfer_referral_get_url() must not be accessed. Any further attempts to extract informatoin from this referral
will fail.
Parameters:
referral The referral to destroy.
Return values:
GLOBUS_SUCCESS The referral was successfully destroyed.
GLOBUS_GASS_TRANSFER_ERROR_NULL_POINTER The referral parameter was GLOBUS_NULL. It could not be destroyed.
Author
Generated automatically by Doxygen for globus gass transfer from the source code.
Version 7.2 Mon Apr 30 2012 Referrals(3)
03-14-2017
