Cowboys TE Jason Witten to Avoid Spleen Surgery

Jason Witten – What has been a physically trying preseason for the Dallas Cowboys got a little better when team doctors informed tight end Jason Witten that he will not need season-ending surgery to repair a lacerated spleen, ESPN reported Wednesday.The bleeding in Witten’s spleen has finally subsided, leading his doctors to believe that it will heal on its own.Witten, who suffered the injury during an Aug. 13 preseason game against the Oakland Raiders, is still aiming to return in time for the Cowboys’ Sept. 5 regular-season opener against New York Giants, but it remains unclear whether he will be ready to play again so soon.A more likely return could be in Week 2, when Dallas plays at Seattle.The news will be welcomed by a team that has been devastated by injuries so far this preseason, particularly throughout its receiving corps. In addition to Witten, Dallas will likely be minus quarterback Tony Romo’s two other top threats in wide receivers Dez Bryant (knee) and Miles Austin (hamstring) until the start of the regular season.Witten, however, is the glue that often keeps the offense together and his loss would have been a major blow to a Dallas team trying to shed its underachieving label of recent years. The nine-year veteran and seven-time Pro Bowl selection is Romo’s unquestioned go-to guy, hauling in 409 passes for 4,824 yards and 21 touchdowns since Romo took over as the starter in 2006.Witten, who is also a key part of the Dallas ground game with his blocking on the edge, has missed just one game in his career because of a fractured jaw he suffered as a rookie in 2003. He’s played through a broken rib, as well as knee and ankle injuries.Witten totaled 79 catches for 942 yards and five touchdowns a year ago, passing Hall of Famer Ozzie Newsome as the tight end with the third-most receptions in NFL history. read more

Suitcase of Cocaine at airport unclaimed

first_imgFacebook Twitter Google+LinkedInPinterestWhatsApp Facebook Twitter Google+LinkedInPinterestWhatsAppBahamas, March 21, 2017 – Nassau – No one has claimed that 13 kilos of cocaine seized on Saturday at the Lynden Pindling International Airport in Nassau; Police says they found it on a routine inspection of luggage with the K9 Unit.  The suitcase was left at the baggage carousel and was found with the large quantity of drugs around 6:30pm.#MagneticMediaNews#cocainefoundatLPIAirport#13kiloscocaineseizedNassauAirport Related Items:#13kiloscocaineseizedNassauAirport, #cocainefoundatLPIAirport, #magneticmedianewslast_img read more

Google Unveils Project Zero an Elite Cybersecurity Squad to Fight Hackers

first_img Google loves a good project.Following in the footsteps of Project Ara, Project Loon and Project Tango, the company has just unveiled a new effort to tackle security issues across the Internet: Project Zero.Security is such a critical priority, the SEO giant is now ramping up earlier part-time work by self-governing staffers — which has led to the discovery of bugs like Heartbleed — into a full-fledged security outfit, the company explained in a blog post yesterday.With Project Zero, Google is looking to extend beyond its own workings on the web and “will work to improve the security of any software depended upon by large numbers of people.”Related: Viral App ‘Yo’ Hires Its HackerAdditionally, all security efforts will be undertaken transparently, with every bug “filed in an external database,” the company said.“We will only report bugs to the software’s vendor — and no third parties,” Google added. “Once the bug report becomes public (typically once a patch is available), you’ll be able to monitor vendor time-to-fix performance, see any discussion about exploitability, and view historical exploits and crash traces.”The name Project Zero refers to a “zero-day” attack or vulnerability, which exploits a previously unknown bug that developers have had no time to patch.Best of all for computer whizzes who want to harness their abilities for the Internet’s greater good? “We’re hiring,” writes Project Zero’s researcher herder, Chris Evans. Interested parties can find out more about the effort on the project’s blog.Related: Why Security Should Be Top of Mind When Creating a Business July 16, 2014 2 min read Free Webinar | Sept. 9: The Entrepreneur’s Playbook for Going Globalcenter_img Growing a business sometimes requires thinking outside the box. Register Now »last_img read more

ChinaBacked Hackers May Have Infiltrated Apples iCloud

first_img Enroll Now for Free Apple Inc’s iCloud storage and backup service in China was attacked by hackers trying to steal user credentials, a Chinese web monitoring group said, adding that it believes the country’s government is behind the campaign.Using what is called a “man-in-the-middle” (MITM) attack, the hackers interposed their own website between users and Apple’s iCloud server, intercepting data and potentially gaining access to passwords, iMessages, photos and contacts, wrote in its blog, a group that conducts research on Chinese Internet censorship, alleged government involvement in the attack, saying it resembled previous attacks on Google Inc, Yahoo Inc and Microsoft Corp’s Hotmail.Asked about the attack, Hua Chunying, a spokeswoman for China’s Foreign Ministry, told a daily news briefing that Beijing was “resolutely opposed” to hacking. She said the Chinese government itself was a major victim of such attacks.The attack cited by Greatfire comes several weeks after Apple said it would begin storing iCloud data for Chinese users on China Telecom servers.It also coincided with the start of iPhone 6 sales in China, which began Friday after weeks of talks between China and Apple over what the government said were cyber security concerns.Two independent security experts contacted by Reuters said Greatfire’s report appeared credible.”All the evidence I’ve seen would support that this is a real attack,” said Mikko Hypponnen, chief research officer at security software developer F-Secure. “The Chinese government is directly attacking Chinese users of Apple’s products.” said the attack most likely could not have been staged without the knowledge of Internet providers like China Telecom, given they appeared to originate from “deep within the Chinese domestic Internet backbone”.But the group said the attack may not be linked to Apple’s recent decision to store user data on China Telecom servers.”The previous MITM attacks all showed the same characteristics as this one,” co-founder Charlie Smith said by email. “Apple did not need to be doing anything with China Telecom for this attack to happen, i.e. the authorities did not need that relationship to stage an attack like this one.”It was unclear if the hackers were still active. Apple did not have an immediate comment when contacted.A China Telecom spokesman said: “The accusation is untrue and unfounded.”Apple said at the time the move to China Telecom was made to improve the speed of service for Chinese servers and flatly denied the possibility that it would expose user data.The United States and Western companies have accused Chinese-backed hackers of infiltrating government and corporate websites and services, but Beijing has repeatedly denied its involvement in such attacks.(Reporting by Jim Finkle in BOSTON and Gerry Shih and Ben Blanchard in BEIJING; Writing by Edwin Chan; Editing by Andre Grenon, Miral Fahmy and Stephen Coates) Free Workshop | August 28: Get Better Engagement and Build Trust With Customers Now October 21, 2014 This story originally appeared on Reuters This hands-on workshop will give you the tools to authentically connect with an increasingly skeptical online audience. 3 min readlast_img read more

Live News traffic and weather updates for North Staffordshire South Cheshire on

first_img Share this video Video Loading Video Unavailable StokeonTrent Live – we’re #localandproudStokeonTrent Live – we’re #localandproudVideo Player is loading.Play VideoPauseUnmute0:00/1:20Loaded: 0%0:00Progress: 0%Stream TypeLIVE-1:20 SharePlayback Rate1xChaptersChaptersDescriptionsdescriptions off, selectedSubtitlessubtitles settings, opens subtitles settings dialogsubtitles off, selectedAudio Trackdefault, selectedFullscreenThis is a modal window.Beginning of dialog window. Escape will cancel and close the window.TextColorWhiteBlackRedGreenBlueYellowMagentaCyanTransparencyOpaqueSemi-TransparentBackgroundColorBlackWhiteRedGreenBlueYellowMagentaCyanTransparencyOpaqueSemi-TransparentTransparentWindowColorBlackWhiteRedGreenBlueYellowMagentaCyanTransparencyTransparentSemi-TransparentOpaqueFont Size50%75%100%125%150%175%200%300%400%Text Edge StyleNoneRaisedDepressedUniformDropshadowFont FamilyProportional Sans-SerifMonospace Sans-SerifProportional SerifMonospace SerifCasualScriptSmall CapsReset restore all settings to the default valuesDoneClose Modal DialogEnd of dialog window.Close Modal DialogThis is a modal window. This modal can be closed by pressing the Escape key or activating the close button.PlayMute0:00/0:00Loaded: 0%Progress: 0%Stream TypeLIVE0:00 Playback Rate1xFullscreenClose Modal DialogThis is a modal window. This modal can be closed by pressing the Escape key or activating the close button. UP NEXT:UP NEXT: Click for Sound Watch Next Video will play in  Click to playTap to playcenter_img The video will start in 1Cancel Play now StokeonTrentLive – we’re #localandproud Watch again We pay for stories! Send your videos to [email protected] to Stoke-on-Trent Live’s breaking news service bringing you all the latest updates from Stoke-on-Trent and North Staffordshire on Friday, August 10. Our team of reporters will be updating this live service with all the latest on the weather, traffic and travel as well as news and entertainment through the day. We’ll be bringing you the very latest updates in our live news feed below. For the latest news and breaking news visit Get all the big headlines, pictures, analysis, opinion and video on the stories that matter to you. Follow us on Twitter @SOTLive – the official Sentinel account – real news in real time. We’re also on Facebook – your must-see news, features, videos and pictures throughout Stoke-on-Trent, North Staffordshire & South Cheshire. You’ll also find us on Instagram here . 15:48There are severe delays on the M6 southbound between J23 and J20.There is a collision involving multiple vehicles on the M6 southbound between J21 and J20 closing 3 of (4) lanes. Traffic officers are on scene and have arranged recovery for the vehicles and contractors to deal with a large amount of debris and spillages in the carriagewayDelays of 2 hours have been reported on the approach. Road users intending on using this section of road are advised to allow plenty of extra time for their journey and to consider alternative routes (if possible).15:39⚠️ If you are heading home from work soon, there are delays on a number of roads across Cheshire, including long delays on the M6 southbound J21-J20 following a road traffic collision.For more information –— Cheshire Police (@cheshirepolice) August 10, 201812:52Broken down vehicle on M6Slow traffic due to earlier broken down vehicle on M6 Southbound between J15 A500 (Stoke-On-Trent) and J14 A5013 (Stafford North). All lanes have been re-opened.Lane one (of three) was closed. All restrictions were lifted around 12:50.12:27One lane shut on A50 near SudburyThere are delays on the A50 Westbound due to an accident near Sudbury, Traffic England reports10:58Police called to 950 incidents involving monkey dust in just three monthsOfficers are called to ten or more incidents a day involving the synthetic drug. More here.10:47Slow traffic on the A34Slow traffic on A34 The Fillybrooks Northbound from A51 (Aston-by-Stone) to Walton Cross (Stone). In the roadworks area.There is a lane closed for electrical work. 10:37Fire service now taking food and drink donations for crews tackling Roaches fireFire crews are asking for donations of non-perishable food and drinks. More here.09:01Accident in CellarheadReports of heavy traffic due to accident on A520 Leek Road near A52 Cellarhead Road (Cellarhead Cross Roads). (Image: Inrix)08:57Slow traffic on A34 in Trent ValeSlow traffic on A34 Newcastle Road between Springfield Retail Park and A500 D Road (Hanford Interchange). 08:04Slow traffic on Werrington RoadSlow traffic on A52 Werrington Road Westbound before A52 Leek Road (Lime Kiln Traffic Lights). 07:57Slow traffic on A53 in Sneyd Green Slow traffic on A53 Cobridge Road Southbound from A5272 Hanley Road (Holden Bridge, Sneyd Green) to A50 Waterloo Road (Cobridge Traffic Lights, Hanley). 06:36M6 slip road reopenedThe slip road has now reopened, according to traffic data company Inrix.06:20M6 slip road still closed due to repair work at junction 13 M6 Southbound exit slip road closed due to emergency repairs at J13 A449 (Stafford South). Traffic is coping well. In the roadworks area.The exit slip road remains closed for nearside barrier repairs following an earlier accident involving a lorry that went down the embankment around 03:00 yesterday. The exit slip road is likely to remain closed until morning rush hour. (Image: Inrix)06:07Weather making Roaches fire worse – a dozen fire engines now at scene12 fire engines are at the scene, roads are closed, one man has been treated for smoke inhalation and the public are being asked to avoid the area, updates as we get them. More here.The fire in the Roaches (Image: Staffordshire Fire and Rescue Service)06:05Good morningWe’ll be bringing you the latest news and traffic updates throughout the morning.last_img read more

What are REST verbs and status codes Tutorial

first_imgThe name Representational state transfer (REST) was coined by Roy Fielding from the University of California. It is a very simplified and lightweight web service compared to SOAP. Performance, scalability, simplicity, portability, and modifiability are the main principles behind the REST design. REST is a stateless, cacheable, and simple architecture that is not a protocol but a pattern. In this tutorial, we will talk about REST verbs and status codes. The article is taken from the book Building RESTful Web services with Go by Naren Yellavula. In this book, you will explore, the necessary concepts of REST API development by building a few real-world services from scratch. REST verbs REST verbs specify an action to be performed on a specific resource or a collection of resources. When a request is made by the client, it should send this information in the HTTP request: REST verb Header information Body (optional) As we mentioned previously, REST uses the URI to decode its resource to be handled. There are quite a few REST verbs available, but six of them are used frequently. They are as follows: GET POST PUT PATCH DELETE OPTIONS If you are a software developer, you will be dealing with these six most of the time. The following table explains the operation, target resource, and what happens if the request succeeds or fails: REST Verb Action Success Failure GET Fetches a record or set of resources from the server 200 404 OPTIONS Fetches all available REST operations 200 – POST Creates a new set of resources or a resource 201 404, 409 PUT Updates or replaces the given record 200, 204 404 PATCH Modifies the given record 200, 204 404 DELETE Deletes the given resource 200 404 The numbers in the Success and Failure columns of the preceding table are HTTP status codes. Whenever a client initiates a REST operation, since REST is stateless, the client should know a way to find out whether the operation was successful or not. For that reason, HTTP has status codes for the response. REST defines the preceding status code types for a given operation. This means a REST API should strictly follow the preceding rules to achieve client-server communication. All defined REST services have the following format. It consists of the host and API endpoint. The API endpoint is the URL path which is predefined by the server. Every REST request should hit that path. A trivial REST API URI: http://HostName/API endpoint/Query(optional) Let us look at all the verbs in more detail. The REST API design starts with the definition of operations and API endpoints. Before implementing the API, the design document should list all the endpoints for the given resources. In the following section, we carefully observe the REST API endpoints using PayPal’s REST API as a use case. GET A GET method fetches the given resource from the server. To specify a resource, GET uses a few types of URI queries: Query parameters Path-based parameters In case you didn’t know, all of your browsing of the web is done by performing a GET request to the server. For example, if you type, you are actually making a GET request to fetch the search page. Here, your browser is the client and Google’s web server is the backend implementer of web services. A successful GET operation returns a 200 status code. Examples of path parameters: Everyone knows PayPal. PayPal creates billing agreements with companies. If you register with PayPal for a payment system, they provide you with a REST API for all your billing needs. The sample GET request for getting the information of a billing agreement looks like this: /v1/payments/billing-agreements/agreement_id. Here, the resource query is with the path parameter. When the server sees this line, it interprets it as I got an HTTP request with a need for agreement_id from the billing agreements. Then it searches through the database, goes to the billing-agreements table, and finds an agreement with the given agreement_id. If that resource exists it sends the details to copy back in response (200 OK). Or else it sends a response saying resource not found (404). Using GET, you can also query a list of resources, instead of a single one like the preceding example. PayPal’s API for getting billing transactions related to an agreement can be fetched with /v1/payments/billing-agreements/transactions. This line fetches all transactions that occurred on that billing agreement. In both, the case’s data is retrieved in the form of a JSON response. The response format should be designed beforehand so that the client can consume it in the agreement. Examples of query parameters are as follows: Query parameters are intended to add detailed information to identify a resource from the server. For example, take this sample fictitious API. Let us assume this API is created for fetching, creating, and updating the details of the book. A query parameter based GET request will be in this format: /v1/books/?category=fiction&publish_date=2017 The preceding URI has few query parameters. The URI is requesting a book from the book’s resource that satisfies the following conditions: It should be a fiction book The book should have been published in the year 2017 Get all the fiction books that are released in the year 2017 is the question the client is posing to the server. Path vs Query parameters—When to use them? It is a common rule of thumb that Query parameters are used to fetch multiple resources based on the query parameters. If a client needs a single resource with exact URI information, it can use Path parameters to specify the resource. For example, a user dashboard can be requested with Path parameters and fetch data on filtering can be modeled with Query parameters. Use Path parameters for a single resource and Query parameters for multiple resources in a GET request. POST, PUT, and PATCH The POST method is used to create a resource on the server. In the previous book’s API, this operation creates a new book with the given details. A successful POST operation returns a 201 status code. The POST request can update multiple resources: /v1/books. The POST request has a body like this: {“name” : “Lord of the rings”, “year”: 1954, “author” : “J. R. R. Tolkien”} This actually creates a new book in the database. An ID is assigned to this record so that when we GET the resource, the URL is created. So POST should be done only once, in the beginning. In fact, Lord of the Rings was published in 1955. So we entered the published date incorrectly. In order to update the resource, let us use the PUT request. The PUT method is similar to POST. It is used to replace the resource that already exists. The main difference is that PUT is idempotent. A POST call creates two instances with the same data. But PUT updates a single resource that already exists: /v1/books/1256 with body that is JSON like this: {“name” : “Lord of the rings”, “year”: 1955, “author” : “J. R. R. Tolkien”} 1256 is the ID of the book. It updates the preceding book by year:1955. Did you observe the drawback of PUT? It actually replaced the entire old record with the new one. We needed to change a single column. But PUT replaced the whole record. That is bad. For this reason, the PATCH request was introduced. The PATCH method is similar to PUT, except it won’t replace the whole record. PATCH, as the name suggests, patches the column that is being modified. Let us update the book 1256 with a new column called ISBN: /v1/books/1256 with the JSON body like this: {“isbn” : “0618640150”} It tells the server, Search for the book with id 1256. Then add/modify this column with the given value. PUT and PATCH both return the 200 status for success and 404 for not found. DELETE and OPTIONS The DELETE API method is used to delete a resource from the database. It is similar to PUT but without any body. It just needs an ID of the resource to be deleted. Once a resource gets deleted, subsequent GET requests return a 404 not found status. Responses to this method are not cacheable (in case caching is implemented) because the DELETE method is idempotent. The OPTIONS API method is the most underrated in the API development. Given the resource, this method tries to know all possible methods (GET, POST, and so on) defined on the server. It is like looking at the menu card at a restaurant and then ordering an item which is available (whereas if you randomly order a dish, the waiter will tell you it is not available). It is best practice to implement the OPTIONS method on the server. From the client, make sure OPTIONS is called first, and if the method is available, then proceed with it. Cross-Origin Resource Sharing (CORS) The most important application of this OPTIONS method is Cross-Origin Resource Sharing (CORS). Initially, browser security prevented the client from making cross-origin requests. It means a site loaded with the URL can only make API calls to that host. If the client code needs to request files or data from, then the second server,, should have a mechanism to recognize to get its resources. This process explains the CORS: requests the OPTIONS method on sends a header like Access-Control-Allow-Origin: in response to the client. Next, can access the resources on without any restrictions that call any REST method. If feels like supplying resources to any host after one initial request, it can set Access control to * (that is, any). The following is the diagram depicting the process happening one after the other: Types of status codes There are a few families of status codes. Each family globally explains an operation status. Each member of that family may have a deeper meeting. So a REST API should strictly tell the client what exactly happened after the operation. There are 60+ status codes available. But for REST, we concentrate on a few families of codes. 2xx family (successful) 200 and 201 fall under the success family. They indicate that an operation was successful. Plain 200 (Operation Successful) is a successful CRUD Operation: 200 (Successful Operation) is the most common type of response status code in REST 201 (Successfully Created) is returned when a POST operation successfully creates a resource on the server 204 (No content) is issued when a client needs a status but not any data back 3xx family (redirection) These status codes are used to convey redirection messages. The most important ones are 301 and 304: 301 is issued when a resource is moved permanently to a new URL endpoint. It is essential when an old API is deprecated. It returns the new endpoint in the response with the 301 status. By seeing that, the client should use the new URL in response to achieving its target. The 304 status code indicates that content is cached and no modification happened for the resource on the server. This helps in caching content at the client and only requests data when the cache is modified. 4xx family (client error) These are the standard error status codes which the client needs to interpret and handle further actions. These have nothing to do with the server. A wrong request format or ill-formed REST method can cause these errors. Of these, the most frequent status codes API developers use are 400, 401, 403, 404, and 405: 400 (Bad Request) is returned when the server cannot understand the client request. 401 (Unauthorized) is returned when the client is not sending the authorization information in the header. 403 (Forbidden) is returned when the client has no access to a certain type of resources. 404 (Not Found) is returned when the client request is on a resource that is nonexisting. 405 (Method Not Allowed) is returned if the server bans a few methods on resources. GET and HEAD are exceptions. 5xx family (server error) These are the errors from the server. The client request may be perfect, but due to a bug in the server code, these errors can arise. The commonly used status codes are 500, 501, 502, 503,  and 504: 500 (Internal Server Error) status code gives the development error which is caused by some buggy code or some unexpected condition 501 (Not Implemented) is returned when the server is no longer supporting the method on a resource 502 (Bad Gateway) is returned when the server itself got an error response from another service vendor 503 (Service Unavailable) is returned when the server is down due to multiple reasons, like a heavy load or for maintenance 504 (Gateway Timeout) is returned when the server is waiting a long time for a response from another vendor and is taking too much time to serve the client For more details on status codes, visit this link: In this article, we gave an introduction to the REST API and then talked about REST has verbs and status codes. We saw what a given status code refers to. Next, to dig deeper into URL routing with REST APIs, read our book Building RESTful Web services with Go. Read Next Design a RESTful web API with Java [Tutorial] What RESTful APIs can do for Cloud, IoT, social media and other emerging technologies Building RESTful web services with Kotlinlast_img read more

Dont look down Swiss open the worlds longest suspension foot bridge

first_img GENEVA — This bridge is not for the acrophobic.Switzerland has inaugurated the world’s longest suspension foot bridge along a trail toward the famed Matterhorn that features majestic Alpine views.A Swiss tourism official said Wednesday the 494-meter (1,621-foot) bridge can cut hiking time on the Europaweg trail by at least 3 hours between the southwestern towns of Graechen and Zermatt.Before Saturday’s opening, Alpine explorers had to descend into the town of Randa and scale another ascent since a shorter foot bridge was closed in 2010 due to unstable terrain.Only 65 centimetres (25 inches) wide, the bridge soars as high as 85 metres (279 feet) above the ground, traversing over the deepest-cut valley in Switzerland.Swiss media said the structure surpasses Germany’s 459-meter (1,506-foot)“Titan-RT” as the world’s longest suspension bridge. Don’t look down: Swiss open the world’s longest suspension foot bridge Share << Previous PostNext Post >> Thursday, August 3, 2017 Tags: Switzerland Source: The Associated Presslast_img read more