Q: How can I use something like ‘echo’ in PHP to output string to response instead of ‘<%=…%>’?
A: Use concat. <% concat “foo” %> will do the same as <%=”foo”%>
Archive for June, 2009
from http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
1xx Informational
Request received, continuing process.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions.
- 100 Continue
- This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request’s headers alone, a client must send
Expect: 100-continueas a header in its initial request (see RFC 2616 §14.20 – Expect header) and check if a100 Continuestatus code is received in response before continuing (or receive417 Expectation Failedand not continue).[2]
- 101 Switching Protocols
- This means the requestor has asked the server to switch protocols and the server is acknowledging that it will do so.[3]
- 102 Processing (WebDAV) (RFC 2518 )
[edit]2xx Success
The action was successfully received, understood, and accepted.
This class of status code indicates that the client’s request was successfully received, understood, and accepted.
- 200 OK
- Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
- 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. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
- 203 Non-Authoritative Information (since HTTP/1.1)
- The server successfully processed the request, but is returning information that may be from another source.
- 204 No Content
- The server successfully processed the request, but is not returning any content.
- 205 Reset Content
- The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requestor reset the document view.
- 206 Partial Content
- The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
- 207 Multi-Status (WebDAV)
- The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
[edit]3xx Redirection
The client must take additional action to complete the request.
This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent should not automatically redirect a request more than five times, since such redirections usually indicate an infinite loop.
- 300 Multiple Choices
- Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, orword sense disambiguation.
- 301 Moved Permanently
- This and all future requests should be directed to the given URI.
- 302 Found
- This is the most popular redirect code[citation needed], but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945 ) required the client to perform a temporary redirect (the original describing phrase was “Moved Temporarily”), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
- 303 See Other (since HTTP/1.1)
- The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
- 304 Not Modified
- Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
- 305 Use Proxy (since HTTP/1.1)
- Many HTTP clients (such as Mozilla[4] and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
- 306 Switch Proxy
- No longer used.
- 307 Temporary Redirect (since HTTP/1.1)
- In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
[edit]4xx Client Error
The request contains bad syntax or cannot be fulfilled.
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. These are typically the most common error codes encountered while online.
- 400 Bad Request
- The request contains bad syntax or cannot be fulfilled.
- 401 Unauthorized
- Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. See Basic access authentication and Digest access authentication.
- 402 Payment Required
- The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.
- 403 Forbidden
- The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
- 404 Not Found
- The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
- 405 Method Not Allowed
- A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
- 406 Not Acceptable
- The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
- 407 Proxy Authentication Required
- 408 Request Timeout
- The server timed out waiting for the request.
- 409 Conflict
- Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
- 410 Gone
- Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a 404 Not Found can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
- 411 Length Required
- The request did not specify the length of its content, which is required by the requested resource.
- 412 Precondition Failed
- The server does not meet one of the preconditions that the requestor put on the request.
- 413 Request Entity Too Large
- The resource that was requested is too large to transmit using the current protocol.
- 414 Request-URI Too Long
- The URI provided was too long for the server to process.
- 415 Unsupported Media Type
- The request did not specify any media types that the server or resource supports. For example the client specified that an image resource should be served as image/svg+xml, but the server cannot find a matching version of the image.
- 416 Requested Range Not Satisfiable
- The client has asked for a portion of the file, but the server cannot supply that portion (for example, if the client asked for a part of the file that lies beyond the end of the file).
- 417 Expectation Failed
- The server cannot meet the requirements of the Expect request-header field.
- 418 I’m a teapot
- The HTCPCP server is a teapot. The responding entity MAY be short and stout. Defined by the April Fools’ specification RFC 2324. See Hyper Text Coffee Pot Control Protocol for more information.
- 422 Unprocessable Entity (WebDAV) (RFC 4918 )
- The request was well-formed but was unable to be followed due to semantic errors.
- 423 Locked (WebDAV) (RFC 4918 )
- The resource that is being accessed is locked
- 424 Failed Dependency (WebDAV) (RFC 4918 )
- The request failed due to failure of a previous request (e.g. a PROPPATCH).
- 425 Unordered Collection
- Defined in drafts of WebDav Advanced Collections, but not present in “Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol” (RFC 3648 ).
- 426 Upgrade Required (RFC 2817 )
- The client should switch to TLS/1.0.
- 449 Retry With
- A Microsoft extension. The request should be retried after doing the appropriate action.
[edit]5xx Server Error
The server failed to fulfil an apparently valid request.
Response status codes beginning with the digit “5″ indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.
- 500 Internal Server Error
- A generic error message, given when no more specific message is suitable.
- 501 Not Implemented
- The server either does not recognise the request method, or it lacks the ability to fulfil the request.
- 502 Bad Gateway
- The server was acting as a gateway or proxy and received an invalid response from the upstream server.
- 503 Service Unavailable
- The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
- 504 Gateway Timeout
- The server was acting as a gateway or proxy and did not receive a timely request from the upstream server.
- 505 HTTP Version Not Supported
- The server does not support the HTTP protocol version used in the request.
- 506 Variant Also Negotiates (RFC 2295 )
- Transparent content negotiation for the request, results in a circular reference.
- 507 Insufficient Storage (WebDAV) (RFC 4918 )
- 509 Bandwidth Limit Exceeded (Apache bw/limited extension)
- This status code, while used by many servers, is not specified in any RFCs.
- 510 Not Extended (RFC 2774 )
- Further extensions to the request are required for the server to fulfil it.
from http://almosteffortless.com/2008/07/21/simple-localization-in-rails-22/
I’ve been staying on the sidelines when it comes to localization in Rails for a while now, but I couldn’t help getting excited about the upcoming native support in Rails 2.2. So, with someguidance from the Rails i18n team, I decided to give things a try.
I’ve been extremely pleased with the results so far, but I’m all ears if anyone would like to offer suggestions on how to better achieve basic localization for a Rails app. Here’s where I’m at so far in a kind of how-to format. This is all plugin-free, using only what’s available in core. I expect that plugins will be coming out to add features and functionality, but you can accomplish quite a bit without any extras.
You can try to follow along, or just get the gist be reading through the steps. As noted in the comments, this is just a proof of concept, is not secure, and shouldn’t be used in production as-is.
1. Make a new Rails app and freeze edge:
~ $ rails i18n ~ $ cd i18n ~ $ rake rails:freeze:edge
2. Make a couple of translation stores (files) in lib/locale directory:
# lib/locale/en-US.rb { 'en-US' => { :hello_world => "Hello World", :hello_flash => "Hello Flash" }} # lib/locale/pirate.rb { 'pirate' => { :hello_world => "Ahoy World", :hello_flash => "Ahoy Flash" }}
3. Set I18n.locale with a before_filter:
# app/controllers/application.rb class ApplicationController < ActionController::Base before_filter :set_locale def set_locale locale = params[:locale] || 'en-US' I18n.locale = locale I18n.load_path += Dir[ File.join(RAILS_ROOT, 'lib', 'locale', '*.{rb,yml}') ] end end
4. Make a controller and route to test things out, using symbols from your translation for user messages:
# config/routes.rb ActionController::Routing::Routes.draw do |map| map.root :controller => 'home', :action => 'index' end # app/controllers/home_controller.rb class HomeController < ApplicationController def index flash[:notice] = :hello_flash end end
5. Create a view using symbols for user messages and use the “t” helper to translate:
# app/views/home/index.html.erb <h1><%=t :hello_world %></h1> <%=t flash[:notice] %> <%= link_to 'en-US', root_path(:locale => 'en-US') %> or <%= link_to 'pirate', root_path(:locale => 'pirate') %>
6. Fire up the old script/server and check it out:
~ $ script/server
I think that about covers it. Of course, this is a very simple example, but it should cover the basics well enough to get started. Please let me know if you have any ideas about how to simplify/improve this, and thanks again to the Rails i18n team for all of their work – everything looks great so far!
Update: You can use YAML to store translations now. Also, the I18n.populate and I18n.store_translations are no longer necessary (or available).
# lib/locale/pirate.yml pirate: hello_world: Ahoy World hello_flash: Ahoy Flash # app/controllers/application.rb I18n.load_path += Dir[ File.join(RAILS_ROOT, 'lib', 'locale', '*.{rb,yml}') ]
Update: Rails 2.2 comes with simple i18n support fully baked in. This is great news because it makes adding internationalization support even easier. Check out the announcement on the Rails site for details, but the short version is that YAML files put into config/locales can be loaded up with a simple call to their file name. Here’s an example:
# config/locales/en.yml en: hello_world: Hello World # config/environment.rb config.i18n.default_locale = :en # app/views/home/index.html.erb <h1><%=t :hello_world %></h1>
from http://blogs.sun.com/divas/entry/no_such_file_to_load
Rails never fails me. As soon as I publish a series of tutorials for a NetBeans release, a new Rails release comes out which breaks my tutorials (and, apparently, most everyone else’s). Gratefully, some customers took the time to click the Feedback button at the end of our tutorials to let us know the tutorials were no longer working. One customer wrote:
“When trying to create the database following the steps indicated, I got an error indicating the mysql gem had been removed from Rails 2.2.2 and that I should install the mysql gem. (Note from me: the actual error message is “The bundled mysql.rb driver has been removed from Rails 2.2. Please install the mysql gem and try again: gem install mysql.”) However, that gem is also native and can’t be installed with JRuby (the misleading directive to do so from NetBeans was really annoying).”
I have to agree that this is indeed REALLY annoying. However, the “misleading directive” comes from Rails, and not from NetBeans. And, since Rails 2.2 came out after NetBeans 6.5, this was an unexpected message.
While the directive may be true for Ruby, it is not true for JRuby, because the the MySQL adapter is included with JRuby. In addition, as the user pointed out, you can’t install the mysql gem with JRuby because you cannot use any gems that build native C libraries during the install process, and that includes the mysql gem.
I did some googling and found two solutions:
- Use the activerecord-jdbcmysql-adapter. You can find the instructions on how to do that here.
- Copy the MySQL driver to your project’s lib folder. If you have an older Rails version, you can copy the Ruby MySQL driver (mysql.rb) from rails-install-dir/gems/activerecord-version/lib/active_record/vendor/mysql.rb to the project’s lib directory. Unfortunately, you have to do this for every JRuby project.
If anyone else has any other solutions, please post a comment.
P.S. For all you Ruby programmers, when you try out a tutorial, you really should pay attention to what gem versions the tutorial was written for. Gem releases such as Rails and RSpec are not always backwards compatible, so there is a chance that the tutorial will not work with releases that came out after the tutorial was written.
It could not just simply remove the session attribute by using invocation removeAttribute.
You have to remove it by setting it to null.
Happen on version 5.1.7, so switch back to 5.1.6 is the solution…
From http://bugs.mysql.com/bug.php?id=41448
| Bug #41448 | java.sql.SQLException: !Statement.GeneratedKeysNotRequested! | ||
|---|---|---|---|
| Submitted: | 13 Dec 2008 18:22 | Modified: | 28 May 20:29 |
| Reporter: | Rico H. | ||
| Status: | Documenting | ||
| Category: | Connector/J | Severity: | S1 (Critical) |
| Version: | 5.1.7 | OS: | Linux |
| Assigned to: | Target Version: | ||
Description: Hello, Consider the following code: PreparedStatement ps = connection.prepareStatement("INSERT INTO table values(?,?)"); ps.setInt(1,value1); ps.setInt(2,value2); ps.executeUpdate(); ResultSet rs = ps.getGeneratedKeys(); // This throws a java.sql.SQLException: !Statement.GeneratedKeysNotRequested! Even when creating the PreparedStament in this other way the same exception is thrown: PreparedStatement ps = connection.prepareStatement("INSERT INTO table values(?,?)",PreparedStatement.RETURN_GENERATED_KEYS); ps.setInt(1,value1); ps.setInt(2,value2); ps.executeUpdate(); ResultSet rs = ps.getGeneratedKeys(); // This ALSO throws a java.sql.SQLException: !Statement.GeneratedKeysNotRequested! According to some posts I read on the Internet, this might be related to Bug #34185, as it seems was pushed into the current 5.1.7 version and the problem didn't happen before. I guess the problem just occurs when using PreparedStaments, as with Statements you can provide the RETURN_GENERATED_KEYS flag when executing the query. However, flags for PreparedStaments can only be provided when "Preparing the Statement". So the following code works well: Statement stmt = connection.createStatement(java.sql.ResultSet.TYPE_FORWARD_ONLY,java.sql.ResultSet.CONCUR_ READ_ONLY); stmt.executeUpdate("INSERT INTO table values(1,2)",Statement.RETURN_GENERATED_KEYS); ResultSet rs = stmt.getGeneratedKeys(); //This works This is breaking lots of apps, and should be fixed as soon as possible. Thank you very much!! How to repeat: See description!