I've been trying to set up an image uploader using Blueimp jQuery File Upload plugin. Everything works fine in my local development environment, but when I deploy my app to a shared hosting environment (000webhost), the ajax requests via DELETE method don't work. I can upload images, but cannot delete them.
I can't find the reason why this is happening. Firebug says that the request is in Aborted status, and I get no response from the server.
I'm using Yii 2.0.12 advanced application template.
What might the issue be? Maybe a problem with the request headers?
This is a screenshot with the info that Firebug provides:
This is my error:
Related
I am using JMeter version 3.2 to perform load testing on a page with HTTPS protocol and I am getting 503 HTTP response code.
On the other hand, when I type the URL on Browser the page is loaded.
Using Chrome Browser I can see the result of the request:
result of the request
The page has been shown. My problem is that I am using HTTP response code on JMeter script to evaluate the response code.
Fistly, does anyone know why I am getting 503 response code even I can see the page?
Secondly, how can I overcome this issue to get Jmeter script rightly done ?
Thanks.
Marcos
JMeter will automatically fail the parent sampler if one of the embedded resources fails to load. This is normal default behaviour and the fact you have HTTP Status Code 503 indicates an error in your application.
There are at least 2 ways of working this around:
Filtering out the "favicon" request using HTTP Request Defaults. On the "Advanced" tab there should be "URLs must match" section which can be used for excluding certain domains from your load test, the relevant regular expression would be something like:
^((?!favicon).ico)*$
Configuring JMeter for not to failing when there is an error in the embedded resources. Add the next line to user.properties file (located in JMeter's "bin" folder)
httpsampler.ignore_failed_embedded_resources=true
JMeter restart will be required to pick the property up.
It's favicon which you may not have in web site.
When you enter web site in browser it can happen too.
Browser search for favicon to show small icon of web site similar to mobile application. Can see cisco answer:
browsers will show an icon to the left of the URL. This known as the
'favicon.ico' and is typically fetched from website.com/favicon.ico.
Your browser will automatically request it when browsing to different
sites
You are actually mostly getting 200 responses. The 503 response is just for the requested resource "favicon.ico" I dont know what that is, but it looks like all the other requests for that page are returning 200. Im guessing favicon.ico is some default image for the ui or something?
I've added Roxy Fileman to my project and tied it in to CKEditor. It's a standard Durandal project with an MVC controller for routing and a web api controller for ajax/json data calls.
A typical working URL for a web api call in my app is http://localhost:63093/api/DurandalApi/getAssessmentQuestionnairePushMenu?id=1
When I try and upload a file from within CKEditor, I get:
Request URL:http://localhost:63093/fileman/index.html?type=image&CKEditor=ckeditor&CKEditorFuncNum=1&langCode=en
Request Method:POST
Status Code:405 Method Not Allowed
Remote Address:[::1]:63093
If, however, I directly go to http://localhost:63093/fileman/index.html?type=image&CKEditor=ckeditor&CKEditorFuncNum=1&langCode=en in my browser, the file upload works perfectly and I can then browse to the image from FileMan inside CKEditor.
The network tab in chrome dev tools indicates that the successful upload is done using this URL: http://localhost:63093/fileman/asp_net/main.ashx?a=UPLOAD which is significantly different to the one that CKEditor attampts to use, but that may be because in the second example, index.html is already loaded?
I'm not completely up to speed with what's going on, but the fact that the same URL works perfectly outside of Durandal if I go directly to the URL seems to indicate the FileMan plugin is working just fine and all permissions are set accordingly. Furthermore the CKEditor config is also fine as it can see the images I upload in the directory, but for some reason it's unable to "post" from within CKEditor (which is embedded in a standard Durandal view).
I'm trying to read up on routing to see if I need to do some kind of exception mapping in Durandal to tell it to let the 3rd party .ashx handler deal with the POST request and I'm not even sure if this problem is indicative of Durandal getting in the way or something else. Any suggestions gratefully received!
Ah. All has become clear. This is a half and half answer really as it doesn't really solve the problem, but equally the problem doesn't really exist!
The issue is that Roxy Fileman does NOT use the CK Editor inbuilt "upload" tab that is in the popup. It expects the user to "browse server" only and use the "add file" link in Roxy instead.
I was confused by the instructions, but now I understand!
I have a question similar to this WebView Windows Store App C# Ajax Not Working
I am loading a local html file onto WebView using :
webView.NavigateToLocalStreamUri(pageUri, localUriResolver_);
I am trying to make a ajax call to remote server. I am getting an error with status=0.
I tried with both jquery and plain XmlHttpRequest, results are same. I am not able to get remote file content.
At the same time, I am able to load local file. As all local files are redirected to my "localUriResolver", i am able to resolve the url and provide the content to ajax call.
Coming to remote content, I know this is cross domain request issue.
Is there a way to get around it on Windows 8.1 WebView. Is there some flag to override the cross-domain origin policy.
Thanks
I believe I am running into the same issue right now. It would appear as though my ajax request is not completing.
I see that our API is hit on our server but the complete callback of my jQuery ajax request is never triggered.
Currently investigating why, please update this if you've found a work around or solution.
I am using Firebug 1.10.2 with Firefox 14.0.1. When showing a web page, the Firebug add-on has this "behavior": Firebug’s “Aborted” message upon Ajax request.
What should I make? Is it so dangerous that I must improve my web application because the presence of some error, or it is a Firebug bug or something else?
Please see the documentation of XHR open() for example here:
https://developer.mozilla.org/en-US/docs/DOM/XMLHttpRequest
Note: Calling this method an already active request (one for which
open()or openRequest()has already been called) is the equivalent of
calling abort().
Just create a new XHR instance whenever you need one. Better yet, use jQuery or other JS library to do AJAX. It should shield you from these intricacies.
I saw this problem when trying to load a JavaScript file using HTTPS, but was serving the site on my local development environment using HTTP. The request to fetch the JavaScript file would fail with the Aborted message in FireBug. Making the requests use the same protocol worked for me.
I'm trying to figure out right configuration for cross origin AJAX call in Safari extension injected script.
My configuration in Extension Builder:
Extension Website Access: All
Include Secure Pages: true
Whitelist: -
Blacklist: -
My goal is to get something like Chromes "permissions": "http://mysite.com/*", and be able to pull user configuration from web service.
note: JSONP drops warning, so I would prefer to avoid it.
Any luck with this? I'm having the same problems. Same setup works fine in the Chrome extension, but hitting Access-Contol-Allow-Origin when trying to do it in Safari Extension.
FIXED - UPDATE:
Hey, I figured out what the problem is. So, it looks like you need to do the cross-domain ajax via the background page. What I end up doing is determining all the requests I need to make in the injected script, then message pass the requests to the background page. The background page listens for messages from the injected script, makes the appropriate ajax calls, and then sends the results via a message to the injected script. The injected script is then listening for messages from the background page, once it gets the message(s) with the ajax results, it takes the appropriate action in the page that's being viewed.