[go: up one dir, main page]

  EconPapers    
Economics at your fingertips  
 

RePEc Data Check for series repec:fpr:fprevi

Each night we check the validity of new and modified templates in the RePEc archives mirrored at EconPapers and run a link checker on a portion of the data. Data for series last updated 2020-09-25 17:23:47 GMT.
  • Data checked 2024-10-27 07:01:45 GMT, 0 errors and 0 warnings. 10 templates without errors.
  • 10 URLs checked 2024-12-14 16:52:56 GMT, 9 errors, 1 warnings
    Papers with bad full text links (File-URL) are not included in NEP.
  • Currently mirrored files for series (login with username datacheck and password repec)
  • Results for the fpr archive.
  • Access statistics for repec:fpr:fprevi.

EconPapers listing for Food policy reviews From International Food Policy Research Institute (IFPRI)
Contact information at EDIRC.

Bibliographic data for series maintained by ().


rdf/redif-files, ReDIF compliance

Templates with errors can not be processed correctly and are dropped. Lines with warnings are ignored when the template is processed.
Consult the ReDIF documentation for further information.

Data checked 2024-10-27 07:01:45 GMT, 0 errors and 0 warnings. 10 templates without errors.
Correcting your data? Use our interactive check to validate your corrections.


 

URL check

10 URLs checked 2024-12-14 16:52:56 GMT, 9 errors, 1 warnings
Papers with bad full text links (File-URL) are not included in NEP.

Errors

Errors indicate bad URLs, the URL should be corrected or removed from the template if the file is no longer available.

  • '500' type errors might be temporary, a count is given for the error if it has persisted for more than one week. In this case the cause (which is typically a DNS error or a problem with the server holding the file) should be investigated and the error corrected.
  • 'bad file descriptor' is a cryptic error message that most likely means that, for a https link, that there is a problem with the SSL certificate. It might be expired or an intermediate certificate is missing from the server.
  • Occassionally an error link might work when you click on it in the browser. Hopefully this is because the error has been resolved. If this condition persists and the links have been checked again (the links for a series are rechecked roughly once a week) here are some likely explanations for the inconsistency:
    • Accesses from the outside are blocked but allowed from within the local network. This needs correcting.
    • Your web server responds differently to HEAD and GET requests, which it should not. We use HEAD requests to check the links because it puts a lighter load on your web server and saves on network bandwidth. Suitable reading for your web server administrator is sections 4.1 and 4.3.2 in RFC 7231 which specify how web servers should behave. If your administrator insists on not implementing HEAD properly he/she should at least configure the server to return a sensible response such as "405 Method Not Allowed" or "501 Not Implemented" so that we can use other methods (a conditional GET) to check the link.
    • The relatively large number of accesses made by the link checker has been identified as suspect by your web server. If so white listing the User-Agent of the link checker should resolve the issue. The User-Agent string is currently "RePEc link checker (https://EconPapers.repec.org/check/)" and you should match on "RePEc link checker" as this will not change.

Errors in series repec:fpr:fprevi

Warnings

Warnings indicate possible problems or errors. Warnings are issued for the following conditions:

  • Redirects: Redirects are used to indicate that a resource has moved to a new location. This is a legitimate use but the redirect is unlikely to stay in place forever so it is a good idea to update the information before the redirect is lost. Unfortunately many webservers are misconfigured to give a redirection status code (3xx) when it should send an error status code (usually 401, 403 or 404). The URL needs correcting if you follow the link and end up on a page mentioning an error code or that the page could not be found.
  • Inconsistent file format: The server indicates that this is a html-document but the extension of the file name is inconsistent with this. This could be a spurious warning but the most likely source of this is a bad URL and a server that is misconfigured to send a '200 OK' response together with a custom error page. If so, the URL should be corrected in the template.

Warnings in series repec:fpr:fprevi

  • repec:fpr:fprevi:3
    • https://www.ifpri.org/cdmref/p15738coll2/id/132291/filename/132505.pdf in element 'File-URL'
      999 Inconsistent file format: Content-Type 'text/html; charset=UTF-8' does not match extension. The URL is redirected: 200 OK (https://www.ifpri.org/cdmref/p15738coll2/id/132291/filename/132505.pdf [301 Moved Permanently]--> https://www.ifpri.org/cdmref/p15738coll2/id/132291/filename/132505.pdf/)
 
Page updated 2024-12-14