Databases
StackOverflow2013
Postsdbo
POBlob upload failing on azure using REST API
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBlob upload failing on azure using REST API
    text
    copied!<p><br/> I have followed this tutorial exactly as it is. <a href="http://www.windowsazure.com/en-us/develop/php/how-to-guides/blob-service/" rel="nofollow">How to use the Blob service from PHP</a></p> <p>Now this works super cool from my localhost. But same set of configs and all stops working when I deploy it to Azure.</p> <p>And the worst part is, the error info I could get after enabling error report on azure is <br/> <strong>HTTP Error 500.0 - Internal Server Error</strong> Nothing else !</p> <p>Please help.!</p> <p>Request Header: <b><br/> GET /index.php/api/blobtest HTTP/1.1<br/> Host: eduora-staging.azurewebsites.net<br/> Connection: keep-alive<br/> Cache-Control: max-age=0<br/> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,<em>/</em>;q=0.8<br/> User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) <br/>Chrome/30.0.1599.101 Safari/537.36<br/> Accept-Encoding: gzip,deflate,sdch<br/> Accept-Language: en-US,en;q=0.8<br/> Cookie: ARRAffinity=f5105030b49455c354a66ad349ab75b57b342f0a8b721d229021b4f0df2e5a15; <br/>WAWebSiteSID=3f247e6be7204ef5a21d5ff5a2248389<br/> </b></p> <p>Response header: <b><br/> HTTP/1.1 500 Internal Server Error<br/> Content-Length: 499<br/> Content-Type: text/html<br/> Server: Microsoft-IIS/8.0<br/> X-Powered-By: PHP/5.3.19<br/> DWAS-Handler-Name: PHP53_via_FastCGI<br/> X-Powered-By: ASP.NET<br/> X-Powered-By: ARR/2.5<br/> X-Powered-By: ASP.NET<br/> Date: Mon, 21 Oct 2013 18:48:12 GMT<br/> </b></p> <p>I could look @ php_errors.log which says <b>[21-Oct-2013 11:20:22 America/Los_Angeles] PHP Fatal error: Class 'WindowsAzure\Common\ServicesBuilder' not found.</b></p> <p>But this class is linked properly from localhost ! </p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload