1 APACHE 2.4 STATUS: -*- mode: text; coding: utf-8 -*-
2 Last modified at [$Date$]
4 The current version of this file can be found at:
6 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
8 The current development branch of this software can be found at:
10 * http://svn.apache.org/repos/asf/httpd/httpd/trunk
12 Consult the following STATUS files for information on related projects:
14 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
15 * http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/STATUS
16 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.4.x/STATUS
17 * http://svn.apache.org/repos/asf/apr/apr/branches/1.5.x/STATUS
18 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.5.x/STATUS
19 * http://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/STATUS
20 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/STATUS
22 Patches considered for backport are noted in their branches' STATUS:
24 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
25 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
29 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
30 while x.{even}.z versions are Stable/GA releases.]
32 2.4.29 : In development.
33 2.4.28 : Tagged on September 25, 2017. Released on October 5, 2017.
34 2.4.27 : Tagged on July 6, 2017. Released on July 11, 2017.
35 2.4.26 : Tagged on June 13, 2017. Released on June 19, 2017.
36 2.4.25 : Tagged on December 16, 2016. Released on December 21, 2016.
37 2.4.24 : Tagged on December 16, 2016, not released.
38 2.4.23 : Tagged on June 30, 2016. Released on July 05, 2016.
39 2.4.22 : Tagged on June 20, 2016, not released.
40 2.4.21 : Tagged on June 16, 2016, not released.
41 2.4.20 : Tagged on April 4, 2016. Released on April 11, 2016.
42 2.4.19 : Tagged on March 21, 2016, not released.
43 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
44 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
45 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
46 2.4.15 : Tagged on June 19, 2015. Not released.
47 2.4.14 : Tagged on June 11, 2015. Not released.
48 2.4.13 : Tagged on June 4, 2015. Not released.
49 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
50 2.4.11 : Tagged on January 15, 2015. Not released.
51 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
52 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
53 2.4.8 : Tagged on March 11, 2014. Not released.
54 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
55 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
56 2.4.5 : Tagged on July 11, 2013, not released.
57 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
58 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
59 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
60 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
61 2.4.0 : Tagged on January 16, 2012, not released.
62 2.3.16 : Tagged on December 15, 2011.
63 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
64 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
65 2.3.13 : Tagged on June 28, 2011, not released.
66 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
67 2.3.11 : Released as Beta on March 7, 2011.
68 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
69 2.3.9 : Tagged on November 23, 2010, not released.
70 2.3.8 : Tagged on August 24, 2010.
71 2.3.7 : Tagged on August 19, 2010, not released.
72 2.3.6 : Released on June 21, 2010.
73 2.3.5 : Released on January 26, 2010.
74 2.3.4 : Released on December 8, 2009.
75 2.3.3 : Tagged on November 11, 2009, not released.
76 2.3.2 : Tagged on March 23, 2009, not released.
77 2.3.1 : Tagged on January 2, 2009, not released.
78 2.3.0 : Tagged on December 6, 2008, not released.
80 Contributors looking for a mission:
82 * Just do an egrep on "TODO" or "XXX" in the source.
84 * Review the bug database at: http://issues.apache.org/bugzilla/
86 * Review the "PatchAvailable" bugs in the bug database:
88 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
90 After testing, you can append a comment saying "Reviewed and tested".
92 * Open bugs in the bug database.
94 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
97 CURRENT RELEASE NOTES:
99 * Forward binary compatibility is expected of Apache 2.4.x releases, such
100 that no MMN major number changes will occur after 2.4.1. Such changes can
101 only be made in the trunk.
103 * All commits to branches/2.4.x must be reflected in SVN trunk,
104 as well, if they apply. Logical progression is commit to trunk
105 then merge into branches/2.4.x, as applicable.
107 * Current exceptions for RTC for this branch:
112 . non-Unix, single-platform code
114 RELEASE SHOWSTOPPERS:
117 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
118 [ start all new proposals below, under PATCHES PROPOSED. ]
120 *) mod_unique_id: Use PRNG output rather than needing to use DNS,
121 an IPv4 address (or failing) and PID, and slowing down startup
123 trunk patch: http://svn.apache.org/r1501827
124 2.4.x patch: trunk works
125 +1: jorton, wrowe, jim
128 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
129 [ New proposals should be added at the end of the list ]
131 *) mod_proxy, mod_ssl: Handle SSLProxy* directives in <Proxy> sections,
132 allowing per backend TLS configuration.
133 trunk patch: http://svn.apache.org/r1740928
134 http://svn.apache.org/r1740960
135 http://svn.apache.org/r1740967
136 http://svn.apache.org/r1740987
137 http://svn.apache.org/r1740998
138 http://svn.apache.org/r1742697
139 http://svn.apache.org/r1756976
140 http://svn.apache.org/r1781313
141 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-r1740928_and_co-v3.patch
143 mrumph: Since this has been sitting for awhile, there are several places
144 where this patch needs to be adjusted against recent changes to 2.4.x.
145 ylavic: With current 2.4.x (r1807662), there seems to be only a conflict with
146 MMN, which can probably be taken by the backporter. I don't see the
147 other places where it needs adjustments, Mike?
148 wrowe: Suspect that this is an MMN Major bump, not minor, without some
149 additional detection/workaround of legacy 2.4 compiled modules.
151 *) mod_remoteip: Add PROXY protocol support
152 trunk patch: http://svn.apache.org/r1776575
153 http://svn.apache.org/r1776578 (doc fix)
154 http://svn.apache.org/r1776627 (shortened name + doc fix)
155 http://svn.apache.org/r1776674 (attribution moved to CHANGES)
156 http://svn.apache.org/r1776740 (attribution updated in mod_remotip.c)
157 http://svn.apache.org/r1778268 (fix compiler warning)
158 http://svn.apache.org/r1780725 (set buckets aside)
159 http://svn.apache.org/r1781030 (fix strict GCC warning)
160 http://svn.apache.org/r1781031 (reference the filter by handle)
161 http://svn.apache.org/r1781701 (rework optional processing case)
162 http://svn.apache.org/r1788674 (final edge cases/ignore slave conns)
163 http://svn.apache.org/r1789800 (remove optional processing)
164 http://svn.apache.org/r1790169 (rename "exception" directive)
165 http://svn.apache.org/r1790457 (Update directive name in err message)
166 http://svn.apache.org/r1806985
167 2.4 convenience patch (includes CHANGES):
168 http://home.apache.org/~jim/patches/RemoteIPProxyProtocol.2.4.x.patch
169 http://svn.apache.org/r1806985
171 mrumph: I had a chance to review this proposal.
172 I committed some suggested changes to trunk in r1806985.
173 Also, the copyright in mod_remoteip.c is of some concern.
174 Perhaps the terms of the copyright should be included in that note.
175 And on a personal note, today is my last day with Oracle.
176 So it may well be my last day with Apache as well.
177 It has been great working with all of you.
178 jim: Not sure what the copyright concern is, but added r1806985
180 ylavic: RemoteIPProxyProtocol* are documented as scoped to server config
181 and virtual host, though using ap_server_conf makes them global
182 only (thus less useful too...).
184 *) mod_journald: Add new module mod_journald to log error logs into journald.
185 trunk patch: http://svn.apache.org/r1610339
186 http://svn.apache.org/r1621806
187 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
189 jchampion: Looks like the headers require GCC extensions to compile, so
190 mod_journald can't be configured in maintainer mode (-std=c89).
191 Can anyone else reproduce, or is it just my distro?
193 *) core/mod_ssl: Add new flag int to module struct. Define first bit for keeping
194 server config records non-shared instances, set for mod_ssl to make manipulations
196 trunk patch: svn merge -c 1809302,1809303,1809305,1809311,1809314,1809713 ^/httpd/httpd/trunk .
197 2.4.x patch: https://svn.apache.org/repos/asf/httpd/httpd/patches/2.4.x/backport-module-flags.diff
198 (merge with alterations for mmn etc.)
201 *) core: A signal received while stopping could have crashed the main
203 trunk patch: http://svn.apache.org/r1809881
204 http://svn.apache.org/r1809973
205 http://svn.apache.org/r1809976
206 http://svn.apache.org/r1812075
207 2.4.x patch: https://svn.apache.org/repos/asf/httpd/httpd/patches/2.4.x/stop_signals-PR61558.patch
208 (merge without changes to motorz)
211 *) configure.in: Latest macOS Xcode 9 installs clang-900, which more
212 fully honors strict-prototypes, which causes AC_CHECK_LIB to
213 fail when --enable-maintainer-mode is set. Also affects clang 5.
214 trunk patch: http://svn.apache.org/r1810448
215 http://svn.apache.org/r1810998
216 2.4.x patch: svn merge -c 1810448,1810998 ^/httpd/httpd/trunk .
219 [This seems to fit into the mold of per-platform quirks which we process
220 in CTR flow, adding my +1 to note that the patch looks sane.]
221 rjung: I think we need this also for GCC, not only recent clang.
222 See my below suggestion (r1812263)
224 *) configure.in: Fix maintainer mode with GCC/Clang.
225 Setting -Wstrict-prototypes in combination with -Werror leads to compiler
226 errors during configure checks (autoconf generates incomplete prototypes).
227 Adding -Wno-error=strict-prototypes lets the compiler tolerate those.
228 Possible future enhancement: remember such "configure time only" flags and
229 remove them from CFLAGS before generating our build time files
230 (Makefile, config_vars.mk etc.), so that the full -Werror is in place
232 trunk patch: http://svn.apache.org/r1812263
233 2.4.x patch: svn merge -c r1812263 ^/httpd/httpd/trunk .
237 PATCHES/ISSUES THAT ARE BEING WORKED
238 [ New entries should be added at the START of the list ]
240 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
241 proxy_post_handshake hook fails.
242 Trunk patch: r1645529 (works)
243 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
245 ylavic: there may be missing bits, see thread for commit r1736510.
247 *) core: Drop an invalid Last-Modified header value coming
248 from a (F)CGI script instead of replacing it with Unix epoch.
249 Warn the users about Last-Modified header value replacements
250 and violations of the RFC.
251 trunk patch: http://svn.apache.org/r1748379
252 http://svn.apache.org/r1750747
253 http://svn.apache.org/r1750749
254 http://svn.apache.org/r1750953
255 http://svn.apache.org/r1751138
256 http://svn.apache.org/r1751139
257 http://svn.apache.org/r1751147
258 http://svn.apache.org/r1757818
259 2.4.x: trunk patches work, final view:
260 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
261 The problem has been discussed in dev@ extensively but we did not reach a common
262 agreement about how to proceed in the long term. While we wait, I would really like
263 to introduce useful logs for the users (the starting point of this change was a users@
264 email thread). If this is not the right way to go I will move the patch to other
265 sections of STATUS (stalled or being worked).
266 The code has been tested with a simple PHP script returning different Last-Modified
267 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
270 *) http: Don't remove the Content-Length of zero from a HEAD response if
271 it comes from an origin server, module or script. Allow the previous
272 behaviour (for legacy/buggy modules only, not origin) by also backporting
273 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
274 comes for free with the same commit).
275 trunk patch: http://svn.apache.org/r1554303
276 http://svn.apache.org/r1678215
277 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
279 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
280 ints added at the end of core_server_config, the proposed merge
281 does a minor bump only.
282 minfrin: Two new directives need to be documented.
284 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
285 fetching the request body, so to minimize the delay between it is supposed
286 to be alive and the first bytes sent: this is a best effort to prevent the
287 backend from closing because of idle or keepalive timeout in the meantime.
288 Also, handle a new "proxy-flushall" environment variable which allows to
289 flush any forwarded body data immediately. PR 56541+37920.
290 trunk patch: http://svn.apache.org/r1656259
291 http://svn.apache.org/r1656359 (CHANGES entry)
292 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
294 -0: jim: This seems to be a hit to normal performance, to handle an
295 error and/or non-normal condition. The pre-fetch is
296 expensive, and is always done, even before we know that
297 the backend is available to rec' it. I understand the
298 error described, but is the fix actually worth it (plus
299 it seems to allow for a DDoS vector).
300 ylavic: It seems to me that the problem is real since we reuse the
301 connection before prefetching 16K (either controlled by the
302 client, or by an input filter), we currently always prefetch
303 these bytes already. Regarding performance I don't see any
304 difference (more cycles) compared with the current code.
305 However I think I failed to rebuild the header_brigade when
306 the proxy loop is retried (ping), so I need to rework this.
307 Do you think we'd better remove the prefetch, or maybe just
308 make it nonblocking (by default)?
309 jim: Non-blocking seems the best way to handle...
311 * mod_dav: Allow other modules to become providers and add ACLs
312 to the DAV response. Requires a release of apr-util v1.6.
313 trunk patch: http://svn.apache.org/r1748322
314 2.4.x: trunk works modulo CHANGES/MMN
316 rpluem asks: Will this compile with apr-util < v1.6 and keep
317 mod_dav working (without the new features of the patch of course)?
318 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
319 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
320 minfrin: Yes, as you can see in the patch everything applies only
321 if APR_XML_X2T_PARSED is defined, and the patch was tested with
322 both apr-util v1.6 and apr-util v1.5.
323 -1: jorton, breaks binary backwards compat per dev@ discuss
324 msgid <20160902120654.GA12674@redhat.com>
325 (& also, making the structure change with apr-util version
326 means it breaks binary compat across an apr-util upgrade?)
328 * Support PCRE2 (10.x) in place of PCRE (8.x).
329 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
331 http://svn.apache.org/r1773454
332 http://svn.apache.org/r1773741
333 http://svn.apache.org/r1773742
334 http://svn.apache.org/r1773839
335 http://svn.apache.org/r1773870
336 http://svn.apache.org/r1773882
337 wrowe notes that the current code is too inefficient, owing to the fact
338 that the ovector is a required allocation and is no longer allocated on
339 the stack, by design. The correct fix is an apr userdata allocation on
340 the appropriate pool, which would be thread-safe, but the actual API of
341 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
342 the ap_regex_t, because a single regex may be used by many threads in
343 parallel and is not thread-safe beyond initialization.
344 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
345 this as a thread safe storage buffer for the majority of cases (<10 $args)
346 and we don't have a portable tls mechanism to do so.
349 PATCHES/ISSUES THAT ARE STALLED
351 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
352 backport keeps syslog logging as part of httpd core and only adds
353 API to allow other modules to be used for error logging.
354 trunk patch: http://svn.apache.org/r1525597
355 http://svn.apache.org/r1525664
356 http://svn.apache.org/r1525845
357 http://svn.apache.org/r1527003
358 http://svn.apache.org/r1527005
359 http://svn.apache.org/r1532344
360 http://svn.apache.org/r1539988
361 http://svn.apache.org/r1541029
362 http://svn.apache.org/r1543979
363 http://svn.apache.org/r1544156
364 http://svn.apache.org/r1626978
365 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
367 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
368 needs 2 args which is not valid in ErrorLog manual)
369 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
370 (sorry, haven't finished reviewing completely)
371 jim: What is the status of this??
373 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
374 and ProxyMatch section to distinguish between normal workers and workers
375 with regex substitutions in the name. Implement handling of such workers
376 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
377 matched and used for request. PR 43513.
378 trunk patch: http://svn.apache.org/r1609680
379 http://svn.apache.org/r1609688
380 http://svn.apache.org/r1641381
381 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
382 Also added missing r1609688 to the patchset.
383 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
385 -0: covener tried to review this one in Austin with Jeff. Does the added match function
386 really cover a very narrow set of parameters with the way it skips over backreferences?
387 Also, why a new API vs. just setting the field inline?
389 * mod_systemd: New module, for integration with systemd on Linux.
390 trunk patch: http://svn.apache.org/r1393976
391 http://svn.apache.org/r1393997
392 http://svn.apache.org/r1484554
393 http://svn.apache.org/r1528032
394 http://svn.apache.org/r1528034
395 http://svn.apache.org/r1614821
396 http://svn.apache.org/r1618579
397 http://svn.apache.org/r1618588
398 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
400 sf comments: The IdleShutdown logic seems broken. Consider a single
401 active connection that is stalled for 10 seconds. That
402 connection will be broken after GracefulShutdownTimeout.
403 A better logic would be to check if there is any open
404 connection that is not in keep-alive state.
406 * core: Add support for systemd socket activation.
407 trunk patch: http://svn.apache.org/r1511033
408 http://svn.apache.org/r1608686
409 http://svn.apache.org/r1608694
410 http://svn.apache.org/r1608703
411 http://svn.apache.org/r1608721
412 http://svn.apache.org/r1608744
413 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
416 * mod_proxy: Ensure network errors detected by the proxy are returned as
417 504 Gateway Timeout as opposed to 502 Bad Gateway
418 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
419 2.4.x patch: trunk patch works modulo CHANGES
421 -1: rpluem: This change is still disputed. See
422 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
424 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
425 compiled by the build compiler instead of the host compiler.
426 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
427 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
428 http://svn.apache.org/viewvc?view=revision&revision=1328390
429 http://svn.apache.org/viewvc?view=revision&revision=1328714
430 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
431 fuankg: on hold until we agree for a better and more simple solution ...
433 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
434 Moved fixing of shebang to separate target so that it is
435 no longer executed by default and all CGIs remain inactive.
436 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
437 http://svn.apache.org/viewvc?view=revision&revision=1421203
438 http://svn.apache.org/viewvc?view=revision&revision=1421591
439 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
442 This commit is essentially deciding that an httpd install on
443 Windows now has printenv/testcgi written in 2 more languages.
444 To the extent that the usefulness is that it shows how to make scripts
445 of these types executable by httpd, I believe that the documentation
446 is the proper place to solve that. To the extent that the usefullness
447 is to show how to implement a CGI in these particular languages, I believe
448 that the httpd distribution and documentation in general is not the
449 place for that. Historically these types of scripts have caused problems
450 for downstream vendorsas well as newbies (and sometimes the intersection
451 of those two groups) who don't understand that these are information leaks
452 once they are enabled, and the subtlety of the way they are disabled ("Apache
453 messed up the first line; let me fix that") contributes to that.
454 fuankg notes: I've just added a big warning to all CGI scripts which should now
455 make absolutely clear that these CGIs are for testing purpose only - so those
456 who enable those scripts with inserting the right shebang should be 100% aware
457 of any risks (this should cover your last point).
458 jim: trawick, does the above address your concerns?
459 trawick: to some extent (somebody reading the script gets an idea)
460 Why isn't the configuration requirement documented instead
461 of described indirectly in a sample?
462 Why are these new samples added to the install without three
463 votes? (I didn't veto it; put your name next to the two
464 existing ones and I'll be satisfied that enough people
465 considered this addition as an appropriate solution for a
466 real httpd usability problem.)
467 wrowe: I'd agree with trawick, and suggest that these scripts can begin
468 their life somewhere in the manual/ tree. This really seems like
469 the place where /usr/share/httpd/examples/ would be useful, but
470 there isn't an ordinary directory for that. Since we want none
471 of the scripts to function 'out of the box', what about a new
472 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
475 * core: block Define and Undefine in vhost and directory context. Because
476 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
477 trunk patch: http://svn.apache.org/r1656063
478 http://svn.apache.org/r1656122
479 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
480 +1: covener (I need to review the docs manually in this area)
481 -1: wrowe (blocking will break "working" .conf files on a subversion update
482 meant to pick up security fixes. "Alerting" I would agree to.)