Skip to content
TheChatArchiveThe Chat Archive
DeepSeekdeepseek-v3-0324· DeepSeekHugging Face LMArena Human Preference 140K

If i ask a LLM in Azure this string "https:// ... /index.html" it gives back 403 while…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Metallama-4-maverick-17b-128e-instruct’s answer.
  1. User

    If i ask a LLM in Azure this string "https:// ... /index.html" it gives back 403 while "https:// ..something. /index.html" is working, why is the string on top special

  2. DeepSeek Assistant

    The behavior you're observing—where a specific URL string like "https:// ... /index.html" returns a 403 (Forbidden) error while a modified version like "https://..something./index.html" works—is likely due to input filtering or security mechanisms in Azure's LLM (or the surrounding infrastructure). Here are the most probable explanations:


    1. URL Pattern Filtering

    • Azure's LLM or its API gateway might have security rules that block certain URL patterns to prevent misuse (e.g., phishing, SSRF attacks, or malicious requests).

    • The string "https:// ... /index.html" could trigger these rules because:

      • The ... might be interpreted as a malformed domain (e.g., resembling a directory traversal ../ or a placeholder for suspicious input).
      • The lack of a valid domain between // and /index.html might flag it as invalid or risky.
    • In contrast, "https://..something./index.html" includes a (nonsensical but syntactically valid) subdomain (..something.), which may bypass strict pattern-matching rules.


    2. SSRF (Server-Side Request Forgery) Protection

    • Azure services often include protections against SSRF attacks, where an attacker tricks a server into making requests to internal resources.
    • A URL with ... might be flagged as an attempt to obfuscate an internal endpoint (e.g., https://internal-service.../index.html), while a more "normal-looking" URL (even with ..something.) is allowed.

    3. Syntax Validation

    • The LLM or its proxy might validate URLs before processing them. The ... could be rejected because:
      • It’s not a valid domain (domains can’t have consecutive dots unless they’re part of a subdomain like sub..example.com, which is still unusual).
      • It resembles a path traversal attempt (e.g., https://example.com/.../index.html could imply moving up directories).

    4. Model-Specific Behavior

    • The LLM itself might have been trained/fine-tuned to reject certain patterns (e.g., incomplete or placeholder URLs) to avoid generating misleading outputs or unsafe content.

    How to Debug Further

    1. Test with Other Patterns: Try variations like:

      • https://example.com/index.html (valid domain)
      • https:// . /index.html (spaces around dots)
      • https://.../index.html (no spaces)
      • This will help isolate whether the issue is with ..., spaces, or the lack of a domain.
    2. Check Azure's Documentation: Look for:

      • Input restrictions for the Azure OpenAI Service or similar LLM offerings.
      • Security policies around URL processing.
    3. Inspect HTTP Headers: If possible, check the full response (headers/body) for the 403 error. Azure might include a Reason header (e.g., Forbidden: SuspiciousPattern).

    4. Contact Azure Support: If this is critical, Azure support can clarify if this is expected behavior due to their security policies.


    Summary

    The 403 is likely due to Azure's infrastructure (not the LLM itself) flagging the ... as a suspicious or malformed pattern. The system is designed to err on the side of blocking potentially risky inputs, even if the intent is benign. Modifying the string slightly (e.g., adding a subdomain) bypasses these checks.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.