Es handelt sich also hier um eine Generatorfunktion, die die „generierende“ Arbeit intern auf etwas anderes überträgt.

    Auf diese Weise können wir das Ganze in einen `with`-Block einfügen und so sicherstellen, dass das dateiartige Objekt nach Abschluss geschlossen wird.

/// tip | Tipp

    assertEquals(1, Iterators.indexOf(iterator, equalTo("mo")));
    assertEquals("jack", iterator.next());
    assertFalse(iterator.hasNext());
  }

  public void testIndexOf_consumedDataWithDuplicates() {
    Iterator<String> iterator = Lists.newArrayList("manny", "mo", "mo", "jack").iterator();
    assertEquals(1, Iterators.indexOf(iterator, equalTo("mo")));
    assertEquals("mo", iterator.next());

{* ../../docs_src/settings/app02_an_py39/main.py hl[17,19:21] *}

### Einstellungen und Tests

Dann wäre es sehr einfach, beim Testen ein anderes Einstellungsobjekt bereitzustellen, indem man eine Abhängigkeitsüberschreibung für `get_settings` erstellt:

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

     */
    @Override
    public SSPContext createContext(CIFSContext tc, String targetDomain, String host, byte[] initialToken, boolean doSigning)
            throws SmbException {
        if (host.indexOf('.') < 0 && host.toUpperCase(Locale.ROOT).equals(host)) {
            // this is not too good, probably should better pass the address and check that it is a netbios one.

        }
        pkgs = System.getProperty("java.protocol.handler.pkgs");
        if (pkgs == null) {
            System.setProperty("java.protocol.handler.pkgs", "jcifs.smb1");
        } else if (pkgs.indexOf("jcifs.smb1") == -1) {
            pkgs += "|jcifs.smb1";
            System.setProperty("java.protocol.handler.pkgs", pkgs);
        }
    }

    // supress javadoc constructor summary by removing 'protected'

            throw new SmbException(fieldName + " exceeds maximum length: " + str.length());
        }

        // Check for null bytes
        if (str.indexOf('\0') != -1) {
            failedValidations.incrementAndGet();
            log.warn("{} contains null bytes", fieldName);
            throw new SmbException(fieldName + " contains null bytes");
        }

The **TLS certificates** are **associated with a domain name**, not with an IP address.

So, to renew the certificates, the renewal program needs to **prove** to the authority (Let's Encrypt) that it indeed **"owns" and controls that domain**.

To do that, and to accommodate different application needs, there are several ways it can do it. Some popular ways are:

* **Modify some DNS records**.

    int start = 0;
    // Iterate through the parts of the ip string.
    // Invariant: start is always the beginning of an octet.
    for (int i = 0; i < IPV4_PART_COUNT; i++) {
      int end = ipString.indexOf(IPV4_DELIMITER, start);
      if (end == -1) {
        end = ipString.length();
      }
      try {
        bytes[i] = parseOctet(ipString, start, end);
      } catch (NumberFormatException ex) {

		</postConstruct>
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"tr/stemmer_override.txt"</arg>
		</postConstruct>
		<!-- fess index -->
		<postConstruct name="addIndexConfig">
			<arg>"fess/doc"</arg>
		</postConstruct>
		<!-- fess_config index -->
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.access_token/access_token"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">

        LaRequestUtil.getOptionalRequest().map(HttpServletRequest::getContextPath).filter(s -> s.length() > 1).ifPresent(s -> sb.append(s));
        sb.append(input);
        if (input.indexOf('?') == -1) {
            try {
                final Long value = resourceHashCache.get(input);
                if (value.longValue() > 0) {
                    sb.append("?t=").append(value.toString());