The URL is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web?

I am trying to upload documents to SharePoint 2010 site and i am getting the following error.

The URL ‘aaa.pdf’ is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web

How can i fix it ?

fsck on non-existent UUID on every boot

I’ve got a problem with XUbuntu 19.04. On every boot, it runs a file system check that times out after 1:30 (killed by systemd) before the boot process continues.

It all started after I installed Debian 10.0 alongside (removed after only one attempt to boot, as it didn’t recognize my video).

The tricky part:

The UUID that it’s trying to check does not exist.

So I can’t simply do a fsck on that drive once it’s finished booting. There is no “trigger file” for “all” file system checks at the root.

I cannot do “tune2fs -l <…>” or “tune2fs -c” on the drive because the drive (the UUID) does not exist.

I already restored the partition to an image from before the issues began – and the file system checks continued. So it seems to be the partitions (why and how and what’s changed?) and not Ubuntu, but… I also have Fedora installed on this computer and it boots without any strange file system checks just fine.

I also tried rebooting into single user mode – the drive’s UUID does not exist there either.

A photo of the file system check:

How can I troubleshoot this? Obviously, I’d like the system to stop trying to fsck a non-existent drive.

iPad doesn’t support a nonexistent peripheral?

Three times tonight, my iPad has popped up “this [vague term] is not supported by this iPad.”

  • Nothing is plugged into the lightning port.
  • A GPS device that can connect was far out of range.
  • my wife’s iPhone is in range but it never connects, and it is almost always in range. If it were that, I’d see this every day.
  • don’t think it’s the WiFi/router, because I witnessed nothing unusual in internet access.

So, ruled out anything I can think of; what might it be that I missed?

Something similar happened another day long ago in a tiny rural village in another country (suggesting it’s not an intrusion attempt).

OWASP ZAP uses non-existent parameters

While running scans with ZAP, I noticed that many of the reported vulnerabilities involve sending malicious content as a value to a parameter named “query”. For example:


The api method in question, however, does not have a parameter that goes by this name, so I was wondering how the tool could possibly detect a vulnerability with this. ZAP did, in fact, report an SQL Injection vulnerability with “Medium” confidence from using a url like the above, and has had similar results with path traversal and xss.

Could this be a consequence of me not setting up ZAP correctly? Is it possible to for an api to be made to read parameters that the developers did not define? Is ZAP just guessing at the parameters the api uses?

ssh to non-existent .local name never times out

If I try to connect to a non-existent .local hostname using most utilities, including ping and telnet, it times out after 5 seconds:

% time telnet host.example.local host.example.local: nodename nor servname provided, or not known telnet host.example.local  0.01s user 0.01s system 0% cpu 5.018 total 

This matches the timeout for the .local config in scutil --dns.

But when I try to ssh to such a hostname, it never times out. (I just Ctrl-C‘d one that was still waiting after 16 minutes.) I can’t figure out any existing option in any of the ssh_config files that would seem to affect hostname resolution. The only option I see that seems relevant is “CanonicalizeHostname“, and it’s not configured in any config file, but I manually set it to “no” with no change in behavior. Adding -v flags to ssh doesn’t reveal any additional information about hostname resolution beyond the fact that it’s “Connecting to host.example.local port 22”, which is the last debug line produced.

I tried capturing the MDNS queries for telnet and ssh. It appears to make an initial query, then wait 1s and ask again, then again 3s later, etc., each retry waiting 3 times longer than the last. telnet gave up after three requests (0s, 1s, and 3s), but ssh got up to the seventh request (0s, 1s, 3s, 9s, 27s, 81s, 243s) before I stopped watching.

I can kind of work around the problem by setting ConnectTimeout 5 in ssh_config (even limiting it to *.local), but that breaks if the name resolution completes but the remote ssh server is slow to respond.

How can I get ssh to timeout name resolution in the same manner as other network tools?

Continuous distributed SMTP auth requests for a non-existent user – any idea what the purpose is?

I have thousands of SMTP auth requests for the same non-existent user, from IP addresses mostly in Argentina. There is rarely more than one hit per IP.

The login will never work because it’s not a valid user, but I’m baffled what the purpose is.

Anybody have any ideas?