Log Out vs Remember Me Post: 302918055

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

It's been awhile...help me remember

Well it's been a long time since I have used any OS besides apples and windows (raising my son). My principal would like our teachers to use UNIX as their mail system. That's not a problem, the mail system is like riding a bike you never forget. Here's my problem. She wants me to write a script...

2. Shell Programming and Scripting

AWK--does anyone remember it

I am trying to run awk on a 55 page Word document. I wanted to delete every occurrence of <company>, <script>, </scripts> from the file then cut & paste all of the appropriate fields to an Excel spreadsheet. Also the code is suppose to replace the dates in a new format such as "xxxx-xx-xx" ...

3. UNIX for Dummies Questions & Answers

remember last visited line in vim

hi, I know we can do this; but dont know how.. I open a file using vim..browse thru it and then say :wq after reaching some line; The next time I open the same file, I want vim to position the cursor on the line where I left last time; anyone?

4. Forum Support Area for Unregistered Users & Account Problems

Two Login's - Remember only one.

Hi All, Have only recently returned to Unix.com due to other activities (*oh the shame of it all). Anyways, when I initially came back to redesigned/revamped site I couldn't remember any of my logins. I'd originally thought that I'd used the UID of 'Cameron' but couldn't remember any details...

5. Shell Programming and Scripting

remember processed files

Hello dear community! I have the following task to accomplish: there is a directory with approximately 2 thousand files. I have to write a script which would randomly extract 200 files on the first run. On the second run it should extract again 200 files but that files mustn't intersect with...

6. Shell Programming and Scripting

parse a log file and remember last line

Hi all: I'm working on a HPUX 11.23 system and I am needing to parse a tomcat-jakarta log file for memory use. Getting the desired data is easy, assuming the log file does not grow. This file grows constantly and I want to check it q 5 min. The next check will pick up from where it left off 5...

7. UNIX for Dummies Questions & Answers

Grep that I should know but I can't remember!

I have a master list of hosts, and a list of bad hosts. I want to filter out the bad hosts from the master list. I was trying a few for loops but it's not providing the desired result: for i in $(cat master_host_list);do grep -iv $i bad_host_list;done | sort | uniq # won't work because it...

8. What is on Your Mind?

Anyone remember this cute unix ad?

It showed a cleaning woman (probably in the evening, after most of the other employees had left work) happily typing commands on a dot matrix terminal (could've been a DEC LA120, IIRC) just because "unix is so easy to use, even a cleaning woman can use it!". If you know where to find a scanned...

9. UNIX for Beginners Questions & Answers

What is the best way to remember UNIX / Linux Commands?

Hi all, I'm new to UNIX world and new to this forum. As I observed there are lot of commands that needs to be remembered in UNIX programming. I'm into DevOps and can anyone please tell me what are all the important commands that are useful for DevOps Engineer. NOTE: Please correct me if my...

LEARN ABOUT PHP

setcookie

SETCOOKIE(3)								 1							      SETCOOKIE(3)

setcookie - Send a cookie

SYNOPSIS

       bool  setcookie	(string   $name,  [string   $value],  [int   $expire],	[string  $path], [string  $domain], [bool  $secure = false], [bool
       $httponly = false])

DESCRIPTION

       setcookie(3) defines a cookie to be sent along with the rest of the HTTP headers. Like other headers, cookies must be sent before any  out-
       put  from  your script (this is a protocol restriction). This requires that you place calls to this function prior to any output, including
       <html> and <head> tags as well as any whitespace.

	Once the cookies have been set, they can be accessed on the next page load with the $_COOKIE or $HTTP_COOKIE_VARS arrays. Note, superglob-
       als such as $_COOKIE became available in PHP 4.1.0. Cookie values also exist in $_REQUEST.

PARAMETERS

	All  the  arguments  except  the $name argument are optional. You may also replace an argument with an empty string ( "") in order to skip
       that argument. Because the $expire argument is integer, it cannot be skipped with an empty string, use a zero ( 0) instead.

       RFC 6265 provides the normative reference on how each setcookie(3) parameter is interpreted.

	      o $name
		- The name of the cookie.

	      o $value
		- The value of the cookie. This value is stored on the clients computer; do not store sensitive information. Assuming the $name is
		'cookiename', this value is retrieved through $_COOKIE['cookiename']

	      o $expire
		-  The	time  the cookie expires. This is a Unix timestamp so is in number of seconds since the epoch. In other words, you'll most
		likely set this with the time(3) function plus the number of seconds before you want it to expire. Or  you  might  use	mktime(3).
		time()+60*60*24*30  will  set  the  cookie to expire in 30 days. If set to 0, or omitted, the cookie will expire at the end of the
		session (when the browser closes).

	      Note

		      You may notice the $expire parameter takes on a Unix timestamp, as opposed to the date format Wdy, DD-Mon-YYYY HH:MM:SS GMT,
		     this is because PHP does this conversion internally.

	      o $path
		-  The	path on the server in which the cookie will be available on. If set to '/', the cookie will be available within the entire
		$domain. If set to '/foo/', the cookie will only be available within the /foo/ directory and all sub-directories such as /foo/bar/
		of $domain. The default value is the current directory that the cookie is being set in.

	      o $domain
		-  The	domain	that the cookie is available to. Setting the domain to 'www.example.com' will make the cookie available in the www
		subdomain and higher subdomains. Cookies available to a lower domain, such as 'example.com' will be  available	to  higher  subdo-
		mains,	such  as 'www.example.com'. Older browsers still implementing the deprecated RFC 2109 may require a leading . to match all
		subdomains.

	      o $secure
		- Indicates that the cookie should only be transmitted over a secure HTTPS connection from the	client.  When  set  to	TRUE,  the
		cookie will only be set if a secure connection exists. On the server-side, it's on the programmer to send this kind of cookie only
		on secure connection (e.g. with respect to $_SERVER["HTTPS"]).

	      o $httponly
		- When TRUE the cookie will be made accessible only through the HTTP protocol. This means that the cookie won't be  accessible	by
		scripting  languages,  such  as  JavaScript. It has been suggested that this setting can effectively help to reduce identity theft
		through XSS attacks (although it is not supported by all browsers), but that claim is often disputed. Added in PHP 5.2.0.  TRUE or
		FALSE

RETURN VALUES

	If  output  exists  prior  to  calling	this function, setcookie(3) will fail and return FALSE. If setcookie(3) successfully runs, it will
       return TRUE. This does not indicate whether the user accepted the cookie.

EXAMPLES

	Some examples follow how to send cookies:

       Example #1

	      setcookie(3) send example

	      <?php
	      $value = 'something from somewhere';

	      setcookie("TestCookie", $value);
	      setcookie("TestCookie", $value, time()+3600);  /* expire in 1 hour */
	      setcookie("TestCookie", $value, time()+3600, "/~rasmus/", "example.com", 1);
	      ?>

	Note that the value portion of the cookie will automatically be urlencoded when you send the cookie, and when it is received, it is  auto-
       matically  decoded  and	assigned  to  a  variable by the same name as the cookie name. If you don't want this, you can use setrawcookie(3)
       instead if you are using PHP 5. To see the contents of our test cookie in a script, simply use one of the following examples:

       <?php
       // Print an individual cookie
       echo $_COOKIE["TestCookie"];
       echo $HTTP_COOKIE_VARS["TestCookie"];

       // Another way to debug/test is to view all cookies
       print_r($_COOKIE);
       ?>

       Example #2

	      setcookie(3) delete example

	       When deleting a cookie you should assure that the expiration date is in the past, to trigger the removal mechanism in your browser.
	      Examples follow how to delete cookies sent in previous example:

	      <?php
	      // set the expiration date to one hour ago
	      setcookie ("TestCookie", "", time() - 3600);
	      setcookie ("TestCookie", "", time() - 3600, "/~rasmus/", "example.com", 1);
	      ?>

       Example #3

	      setcookie(3) and arrays

	       You  may  also  set array cookies by using array notation in the cookie name. This has the effect of setting as many cookies as you
	      have array elements, but when the cookie is received by your script, the values are all placed in an array with the cookie's name:

	      <?php
	      // set the cookies
	      setcookie("cookie[three]", "cookiethree");
	      setcookie("cookie[two]", "cookietwo");
	      setcookie("cookie[one]", "cookieone");

	      // after the page reloads, print them out
	      if (isset($_COOKIE['cookie'])) {
		  foreach ($_COOKIE['cookie'] as $name => $value) {
		      $name = htmlspecialchars($name);
		      $value = htmlspecialchars($value);
		      echo "$name : $value <br />
";
		  }
	      }
	      ?>

	      The above example will output:

	      three : cookiethree
	      two : cookietwo
	      one : cookieone

CHANGELOG

       +--------+---------------------------------------------------+
       |Version |						    |
       |	|						    |
       |	|		     Description		    |
       |	|						    |
       +--------+---------------------------------------------------+
       | 5.5.0	|						    |
       |	|						    |
       |	|  A Max-Age attribute is now included in the  Set- |
       |	| Cookie header sent to the client.		    |
       |	|						    |
       | 5.2.0	|						    |
       |	|						    |
       |	|	  The $httponly parameter was added.	    |
       |	|						    |
       +--------+---------------------------------------------------+
NOTES

       Note

	       You  can  use  output  buffering  to send output prior to the call of this function, with the overhead of all of your output to the
	      browser being buffered in the server until you send it. You can do this by calling ob_start(3) and ob_end_flush(3) in  your  script,
	      or setting the output_buffering configuration directive on in your php.ini or server configuration files.

       Note

	       If  the	PHP  directive	register_globals  is set to on then cookie values will also be made into variables. In our examples below,
	      $TestCookie will exist. It's recommended to use $_COOKIE.

	Common Pitfalls:

	      o Cookies will not become visible until the next loading of a page that the cookie should be visible for. To test if  a  cookie  was
	      successfully  set, check for the cookie on a next loading page before the cookie expires. Expire time is set via the $expire parame-
	      ter. A nice way to debug the existence of cookies is by simply calling
		print_r($_COOKIE);.

	      o Cookies must be deleted with the same parameters as they were set with. If the value argument is an empty string, or
		FALSE, and all other arguments match a previous call to setcookie, then the cookie with the specified name will  be  deleted  from
		the remote client. This is internally achieved by setting value to 'deleted' and expiration time to one year in past.

	      o Because setting a cookie with a value of
		FALSE will try to delete the cookie, you should not use boolean values. Instead, use 0 for FALSE and 1 for TRUE.

	      o Cookies names can be set as array names and will be available to your PHP scripts as arrays but separate cookies are stored on the
	      user's system. Consider explode(3) to set one cookie with multiple names and values. It is not recommended to use  serialize(3)  for
	      this purpose, because it can result in security holes.

	Multiple calls to setcookie(3) are performed in the order called.

SEE ALSO

       header(3), setrawcookie(3), cookies section, RFC 6265, RFC 2109.

PHP Documentation Group 													      SETCOOKIE(3)