|
|
Aerospace Engineering Online: Technology update: July 2000
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 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. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
|
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 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. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
|
Technology update (July 2000)
- F-2 contract award, - Lockheed Martin Aeronautics Co.
- Fiber-optic acoustic strain measurement, - NTS/IOS
- Components delivered for third X-34 ,- Vermont Composites Inc.
- New technologies selected for research program, - NASA Office of Aero-Space Technology
- Coming to the surface, - BAE Systems
- Round up, - Furmanite
- A318 tests, - Airbus
- Double act robot, - System 3R
- Fast track, - Brookhouse Holdings
- Virtual cockpit technology, - Microvision, Inc.
- Navy C-40A makes first flight, - Boeing
- New military helicopter engine program, - General Electric Co./United Technologies Corp.
- KTX-2 fuel system bundle, - Argo-Tech Corp.
- Head-up Guidance System for Challenger 604
|
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 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. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
|
|
