King Wooper Admin
Number of posts : 6710 Age : 28
| Subject: Codes October 18th 2008, 2:42 pm | |
| Here are the forum codes [Including the Username one I used on the Homepage Message] Remember to put these inside {}! FORUM : # FORUMURL : wooperspond.forumotion.com (Forum Address) # FORUMURLINK : wooperspond.forumotion.com (Link) # FORUMNAME : Wooper's Pond Forums! (Forum name) # FORUMNAMELINK : Wooper's Pond Forums! (Link) # FORUMDESC : Halloween is coming! (Site Description) # FORUMBIRTHDAY : Wed 7 Nov 2007 - 17:07 (Board started) # FORUMAGE : 346 (Board up days) # FORUMCOUNTFORUM : (Number of forums/categories) # FORUMCOUNTOPIC : (Number of topics) # FORUMCOUNTPOST : (Number of posts) # FORUMCOUNTUSER : (Number of users) # FORUMONLINEUSER : (Most users ever online) # FORUMONLINEDATE : (Most users ever online date) # FORUMLASTUSER : (Latest user registered) # FORUMLASTUSERLINK : (Link) USERS : # USERNAME : (Username) # USERLINK: (View user profile) # USERBIRTHDAY : (Birthday) # USERAGE : (Age) # USERREGDATE : (Joined) # USERLASTVISIT : (Last visit) # USERCOUNTPOST : (Total posts) In connection with the variables {USER...}: they will each time concern the user who reads them except at the time of sending of an email where the posted values will be those of the shipper. I hope you enjoy using them. - King Wooper
Last edited by King Wooper on October 18th 2008, 2:47 pm; edited 1 time in total | |
|
Chad
Number of posts : 4 Age : 35
| Subject: Re: Codes October 18th 2008, 2:45 pm | |
| | |
|
King Wooper Admin
Number of posts : 6710 Age : 28
| Subject: Re: Codes October 18th 2008, 2:46 pm | |
| You're welcome, but less than five word posts are spam.
Read the rules, ok? | |
|
Chad
Number of posts : 4 Age : 35
| Subject: Re: Codes October 18th 2008, 4:11 pm | |
| oh, i am sorry about that. So do you know the code to show the viewers ip address? i remember there where ones that showed your ip address and your home state, even your web browser. people would freak out because they hadnt realized that they are the only ones who can see it. | |
|
King Wooper Admin
Number of posts : 6710 Age : 28
| Subject: Re: Codes October 18th 2008, 6:06 pm | |
| I don't remember it...let me do a quick search, OK? EDIT: <%= Request.ServerVariables("Remote_Addr")%> That code works for a page with both HTML and ASP, but not for pure HTML or pure ASP. EDIT 2: The variables on the first post are the only ones that work on Forumotion. If you want them for use on another site: - Code:
-
ALL_HTTP All HTTP headers sent by the client.
ALL_RAW Retrieves all headers in raw form. The difference between ALL_RAW and ALL_HTTP is that ALL_HTTP places an HTTP_ prefix before the header name and the header name is always capitalized. In ALL_RAW the header name and values appear as they are sent by the client.
APPL_MD_PATH Retrieves the metabase path for the Application for the ISAPI DLL.
APPL_PHYSICAL_PATH Retrieves the physical path corresponding to the metabase path. IIS converts the APPL_MD_PATH to the physical (directory) path to return this value.
AUTH_PASSWORD The value entered in the client's authentication dialog. This variable is available only if Basic authentication is used.
AUTH_TYPE The authentication method that the server uses to validate users when they attempt to access a protected script.
AUTH_USER The name of the user as it is derived from the authorization header sent by the client, before the user name is mapped to a Windows account. This variable is no different from REMOTE_USER. If you have an authentication filter installed on your Web server that maps incoming users to accounts, use LOGON_USER to view the mapped user name.
CERT_COOKIE Unique ID for client certificate, returned as a string. Can be used as a signature for the whole client certificate.
CERT_FLAGS bit0 is set to 1 if the client certificate is present.
bit1 is set to 1 if the cCertification authority of the client certificate is invalid (it is not in the list of recognized CAs on the server).
CERT_ISSUER Issuer field of the client certificate (O=MS, OU=IAS, CN=user name, C=USA).
CERT_KEYSIZE Number of bits in Secure Sockets Layer connection key size. For example, 128.
CERT_SECRETKEYSIZE Number of bits in server certificate private key. For example, 1024.
CERT_SERIALNUMBER Serial number field of the client certificate.
CERT_SERVER_ISSUER Issuer field of the server certificate.
CERT_SERVER_SUBJECT Subject field of the server certificate.
CERT_SUBJECT Subject field of the client certificate.
CONTENT_LENGTH The length of the content as given by the client.
CONTENT_TYPE The data type of the content. Used with queries that have attached information, such as the HTTP queries GET, POST, and PUT.
GATEWAY_INTERFACE The revision of the CGI specification used by the server. The format is CGI/revision.
HTTP_<HeaderName> The value stored in the header HeaderName. Any header other than those listed in this table must be prefixed by HTTP_ in order for the ServerVariables collection to retrieve its value. Note The server interprets any underscore (_) characters in HeaderName as dashes in the actual header. For example if you specify
HTTP_MY_HEADER, the server searches for a header sent as MY-HEADER.
HTTP_ACCEPT Returns the value of the Accept header.
HTTP_ACCEPT_LANGUAGE Returns a string describing the language to use for displaying content.
HTTP_COOKIE Returns the cookie string that was included with the request.
HTTP_HOST Returns the name of the Web server. This may or may not be the same as SERVER_NAME depending on type of name resolution you are using on your Web server (IP address, host header).
HTTP_REFERER Returns a string that contains the URL of the page that referred the request to the current page using an HTML <A> tag. Note that the URL is the one that the user typed into the browser address bar, which may not include the name of a default document. If the page is redirected, HTTP_REFERER is empty. HTTP_REFERER is not a mandatory member of the HTTP specification.
HTTP_USER_AGENT Returns a string describing the browser that sent the request.
HTTPS Returns ON if the request came in through secure channel (SSL) or it returns OFF if the request is for a non-secure channel.
HTTPS_KEYSIZE Number of bits in Secure Sockets Layer connection key size. For example, 128.
HTTPS_SECRETKEYSIZE Number of bits in server certificate private key. For example, 1024.
HTTPS_SERVER_ISSUER Issuer field of the server certificate.
HTTPS_SERVER_SUBJECT Subject field of the server certificate.
INSTANCE_ID The ID for the IIS instance in textual format. If the instance ID is 1, it appears as a string. You can use this variable to retrieve the ID of the Web-server instance (in the metabase) to which the request belongs.
INSTANCE_META_PATH The metabase path for the instance of IIS that responds to the request.
LOCAL_ADDR Returns the Server Address on which the request came in. This is important on multi-homed computers where there can be multiple IP addresses bound to the computer and you want to find out which address the request used.
LOGON_USER The Windows account that the user is impersonating while connected to your Web server. Use REMOTE_USER or AUTH_US<CODE>ER to view the raw user name that is contained in the request header. The only time LOGON_USER holds a different value than these other variables is if you have an authentication filter installed.
PATH_INFO Extra path information as given by the client. You can access scripts by using their virtual path and the PATH_INFO server variable. If this information comes from a URL, it is decoded by the server before it is passed to the CGI script.
PATH_TRANSLATED A translated version of PATH_INFO that takes the path and performs any necessary virtual-to-physical mapping.
QUERY_STRING Query information stored in the string following the question mark (?) in the HTTP request.
REMOTE_ADDR The IP address of the remote host making the request.
REMOTE_HOST The name of the host making the request. If the server does not have this information, it will set REMOTE_ADDR and leave this empty.
REMOTE_USER The name of the user as it is derived from the authorization header sent by the client, before the user name is mapped to a Windows account. If you have an authentication filter installed on your Web server that maps incoming users to accounts, use LOGON_USER to view the mapped user name.
REQUEST_METHOD The method used to make the request. For HTTP, this is GET, HEAD, POST, and so on.
script_NAME A virtual path to the script being executed. This is used for self-referencing URLs.
SERVER_NAME The server's host name, DNS alias, or IP address as it would appear in self-referencing URLs.
SERVER_PORT The port number to which the request was sent.
SERVER_PORT_SECURE A string that contains either 0 or 1. If the request is being handled on the secure port, then this will be 1. Otherwise, it will be 0.
SERVER_PROTOCOL The name and revision of the request information protocol. The format is protocol/revision.
SERVER_SOFTWARE The name and version of the server software that answers the request and runs the gateway. The format is name/version. URL Gives the base portion of the URL.
Phew...Remember to put the variables on the context: <%= Request.ServerVariables("Remote_Addr")%> Replacing the Remote_Addr by the one you wish. Well, I guess I'll return here when I need the codes, as I've used a bunch of my documents... I wonder if someone else here understands this . | |
|
Lexicon Uber Wooper
Number of posts : 3927 Age : 27
| Subject: Re: Codes October 19th 2008, 2:02 am | |
| NOPE. I have absolutely no idea what's going on. But nice work for adding a Tech part. :) | |
|
jasp10agosto Global Moderator
Number of posts : 2449 Age : 30
| Subject: Re: Codes October 21st 2008, 6:40 am | |
| And those codes are for..?!?! | |
|
King Wooper Admin
Number of posts : 6710 Age : 28
| Subject: Re: Codes October 21st 2008, 7:18 am | |
| A lot of things...just read them. | |
|