Friday, February 18, 2005
Gmail an ultimate product from google is now rolled out to all users who gave their email ID to google, Initially gmail was registered only be invites, First set of invitation was sent out to adwords and adsense advertisers slowly a massive webmaster crowd started using Gmail,
Got the following mail to one of the account where our email ID was given to google,
Got the following mail to one of the account where our email ID was given to google,
Hi there,
Thanks for signing up to be updated on the latest Gmail
happenings. We hope it's been worth the wait, because we're excited to finally
offer you an invitation to open a free Gmail account! Just click on this link to
create your new account:
gmail.google.com/**** Since last April, we've been
working hard to create the best email service possible. It already comes with
1,000 megabytes of free storage, powerful Google search technology to find any
message you want instantly, and a new way of organizing email that saves you
time and helps you make sense of all the information in your inbox.
And here
are just some of the things that we've added in the last few months:
- Free
POP access: Take your messages with you. Download them, read them offline,
access them using Outlook, your Blackberry or any other device that supports
POP
- Gmail Notifier: Get new mail notifications and see the messages and
their senders without having to open a browser
- Better contacts management:
Import your contacts from Yahoo! Mail, Hotmail, Outlook, and others to Gmail in
just a few clicks. Add phone numbers, notes and more. Even use search to keep
better track of it all.
We also wanted to thank you. For showing us your
support and for being so patient. And to those who have already signed up for
Gmail, thank you for giving it a try and for helping us make it better. Our
users are what have made this product great. So whether you're just signing up
for your account or you've been with us since the beginning, keep letting us
know how we can build you the best email service around.
That's it for now.
We hope you like Gmail and will share it with your friends. We've got lots of
cool new stuff planned and we can't wait for you to see our work in your Gmail
accounts! Stay tuned...
Thanks,The Gmail Team
==We sent you this message
because you signed up to be updated on Gmail. If you do not wish to receive such
updates in the future, you may opt-out of receiving Gmail updates by visiting:
(If clicking the URLs in this message does not work, copy and paste them into
the address bar of your browser)
1600 Amphitheatre ParkwayMountain View, CA
94043
Now it has started reaching not too web savvy users too,
Google has recently sent out 50 invitations per active User ID,
Think slowly gmail will be available to general public, If they make it
public they have to handle 1000s to millions of registrations, So they will give
a deep thinking before making it public, Anyway everything is google news,
Http list of header status Important tip of the header status of a site - seo tip friday 18 feb 2005
list of HTTP status :-
100 Continue
The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server.
101 Switching Protocols
The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection
200 OK
The request has succeeded. The information returned with the response is dependent on the method used in the request
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
201 Created
The request has been fulfilled and resulted in a new resource being created.
202 Accepted
The request has been accepted for processing, but the processing has not been completed.
203 Non-Authoritative Information
The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy.
204 No Content
The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.
205 Reset Content
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent.
206 Partial Content
The server has fulfilled the partial GET request for the resource.
300 Multiple Choices
The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.
302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
303 See Other
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource.
304 Not Modified
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code.
305 Use Proxy
The requested resource MUST be accessed through the proxy given by the Location field.
306 (Unused)
The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.
307 Temporary Redirect
The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
400 Bad Request
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
401 Unauthorized
The request requires user authentication.
402 Payment Required
403 Forbidden
The server understood the request, but is refusing to fulfill it.
404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
406 Not Acceptable
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
408 Request Timeout
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
409 Conflict
The request could not be completed due to a conflict with the current state of the resource.
410 Gone
The requested resource is no longer available at the server and no forwarding address is known.
411 Length Required
The server refuses to accept the request without a defined Content- Length.
412 Precondition Failed
The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
413 Request Entity Too Large
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
414 Request-URI Too Long
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
415 Unsupported Media Type
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
416 Requested Range Not Satisfiable
A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field.
417 Expectation Failed
The expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
10.5.2
501 Not Implemented
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
SEO Blog Team,
100 Continue
The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server.
101 Switching Protocols
The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection
200 OK
The request has succeeded. The information returned with the response is dependent on the method used in the request
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
201 Created
The request has been fulfilled and resulted in a new resource being created.
202 Accepted
The request has been accepted for processing, but the processing has not been completed.
203 Non-Authoritative Information
The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy.
204 No Content
The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.
205 Reset Content
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent.
206 Partial Content
The server has fulfilled the partial GET request for the resource.
300 Multiple Choices
The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.
302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
303 See Other
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource.
304 Not Modified
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code.
305 Use Proxy
The requested resource MUST be accessed through the proxy given by the Location field.
306 (Unused)
The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.
307 Temporary Redirect
The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
400 Bad Request
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
401 Unauthorized
The request requires user authentication.
402 Payment Required
403 Forbidden
The server understood the request, but is refusing to fulfill it.
404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
406 Not Acceptable
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
408 Request Timeout
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
409 Conflict
The request could not be completed due to a conflict with the current state of the resource.
410 Gone
The requested resource is no longer available at the server and no forwarding address is known.
411 Length Required
The server refuses to accept the request without a defined Content- Length.
412 Precondition Failed
The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
413 Request Entity Too Large
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
414 Request-URI Too Long
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
415 Unsupported Media Type
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
416 Requested Range Not Satisfiable
A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field.
417 Expectation Failed
The expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
10.5.2
501 Not Implemented
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
SEO Blog Team,
